Use web3 IPCProvider instead of HTTP Provider #13

Closed
opened 2017-06-21 10:35:39 +00:00 by bumi · 2 comments
bumi commented 2017-06-21 10:35:39 +00:00 (Migrated from github.com)

As our hubot runs on the same machine as the parity node we could directly connect to parity using the IPC provider - instead of through HTTP.
I assume this might be a bit more performant and reliable? causing less http requests?

https://github.com/ethereum/web3.js/blob/master/lib/web3/ipcprovider.js

As our hubot runs on the same machine as the parity node we could directly connect to parity using the IPC provider - instead of through HTTP. I assume this might be a bit more performant and reliable? causing less http requests? https://github.com/ethereum/web3.js/blob/master/lib/web3/ipcprovider.js
raucao commented 2017-06-21 17:50:08 +00:00 (Migrated from github.com)

It would probably also enable synchronous method calls, which is a bit of a PITA when it's missing.

It would probably also enable synchronous method calls, which is a bit of a PITA when it's missing.
raucao commented 2018-04-22 11:11:35 +00:00 (Migrated from github.com)

Not running Parity anymore.

Not running Parity anymore.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kredits/hubot-kredits#13