Feature: WebSocket Provider

[youfoundron]

Issue Type

• Bug (https://github.com/ethjs/ethjs/blob/master/.github/CONTRIBUTING.md#bug-reports)
• Feature (https://github.com/ethjs/ethjs/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description

Love love love this API, so much nicer to work with than web3.js.
Really hoping to see an ethjs-provider-wss module in the near future! 😁

[SilentCicero]

There will be a round of bounties for it coming up. It's on the list.

…

Sent from my iPhone

On Feb 5, 2018, at 10:21 PM, Ron Gierlach ***@***.***> wrote: Issue Type Bug (https://github.com/ethjs/ethjs/blob/master/.github/CONTRIBUTING.md#bug-reports) Feature (https://github.com/ethjs/ethjs/blob/master/.github/CONTRIBUTING.md#feature-requests) Description Love love love this API, so much nicer to work with than web3.js. Really hoping to see an ethjs-provider-wss module in the near future! 😁 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[sulliwane]

the killer feature of the new web3js@1.0.0 is the support for websocket providers. But web3js@1.0.0 comes at a price, it's +100KB bigger than ethjs. Here is the result of npm run build in react project:

+web3@1.0.0.beta30 => +170.26 KB
+ethjs@0.3.3  => +62.94 KB

Given that Infura just recenlty added support for websocket => wss://rinkeby.infura.io/ws, we could now enjoy:
1- Enable use of filters eth_newFilter (available on infura websocket only)
2- Reduce network traffic when watching events (ws VS http polling)

Please upvote this issue to show your interest in a ws provider for ethjs 👍

[Sowmayjain]

Any updates?

[SilentCicero]

The websockets provider requires a lot of management, I would need to think about the API more. It might be that we just do a separate socket lib for now, which falls back on rpc under failure.

…

Sent from my iPhone

On Aug 6, 2018, at 10:49 AM, Sowmay Jain ***@***.***> wrote: Any updates? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.