Issue 189 | Add WebsocketProvider

[ryan-rowland]

#189

Happy path implementation. Specific errors and error codes haven't been observed or considered. A cheat sheet on which errors to expect and how to handle them would be helpful.

Works against test networks. Mainnet seems to want to disconnect the websocket almost immediately on each connection, causing some data loss. We should hold off on merging until we figure out why this is.

Test by running node example.js, which runs both FetchProvider and WebsocketProvider side by side to compare results.

[ryan-rowland]

@danfinlay Looks like there may be an issue with wss://mainnet.infura.io/ws. All of the other endpoints, including wss://mainnet.infura.io/_ws, work fine. Could I get a review based on the assumption the main endpoint is broken and will be updated?

PS: looks like circleCI is currently broken for this repo, causing a few approved PRs to not be merged.

[kumavis]

does the ws endpoint not accept this key?

[ryan-rowland]

It does, but looking at the RPC over WebSocket spec I saw this was missing from requests and figured it better to be exact.

[kumavis]

Added the websocket provider from this pull request, thank you

[ghost]

@kumavis , I tried to spot the relevant commit, but failed. Which is it?

[ryan-rowland]

@lazaridiscom Looks like it's here 5861341

And there are a few follow-up commits making some adjustments.

Thanks for the update @kumavis