Use web3 IPCProvider instead of HTTP Provider #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
It would probably also enable synchronous method calls, which is a bit of a PITA when it's missing.
Not running Parity anymore.