Feature: WebSocket Provider #20

Activity

1. SilentCicero commented on Feb 5, 2018

   

   SilentCicero

   on Feb 5, 2018 via email

   Member

   More actions

   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.

   👍React with 👍2Reacted by Sulliwane and decodedbrain

   🎉React with 🎉2Reacted by ron e.g. and Sulliwane
2. sulliwane commented on Mar 12, 2018

   

   sulliwane

   on Mar 12, 2018

   More actions

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

   [email protected] => +170.26 KB
   [email protected]  => +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 👍

   👍React with 👍9Reacted by Sindélio Henrique Lima, coinsandsteeldev, Mason Fischer, Lib, Junichi Sugiura, decodedbrain, Sulliwane, Hakeem Orewole and Paul Pham
3. Sowmayjain commented on Aug 6, 2018

   

   Sowmayjain

   on Aug 6, 2018

   More actions

   Any updates?
4. SilentCicero commented on Aug 6, 2018

   

   SilentCicero

   on Aug 6, 2018 via email

   Member

   More actions

   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.