Spil of now Poloniex exchange only has one open socket that sends back all gegevens.
** Ronaldo Barbachano, 2018 **
Combines public crypto currency websocket API’s to provide a low-resource, zero configuration ticker. Each exchange, except for bittrex, uses a realtime websocket.
- Get ticker quotes via cryptoSocket.echoExchange() or access object variable cryptoSocket.Exchanges
Starts a websocket. Where exchange is always lowercase and symbol is always upper-case.
Pass an array to subscribe to numerous markets
Thesis exchanges should support all markets that they have, and will be ordinary to add more.
Spil of now Poloniex exchange only has one open socket that sends back all gegevens. The above syntax is not recommeneded unless you are only following one symbol, spil it will open up numerous sockets that comeback all gegevens, and filterzakje out your selections.
A elementary printout of all open ticker quotes.
Access to the raw variable the module uses to store ticker quotes spil they update. One value at a time.
** Does this store gegevens? **
Nope. Ticker values (te most cases last sale price) is stored ter memory.
Other popular BTC media modules require incredible amount of bandwidth at regular intervals which can make deployment difficult te many situations. Websockets are obviously the way to go for efectivo time gegevens, spil permanently querying many exchanges can be taxing.
This module does not include exchange API’s that do not have web sockets. Why? Theres a billion other modules that do something similar, and perhaps this is a wake up call to any exchange that does not suggest rhobust websocket support.
Many developers would rather not be bothered reading through extra API documentation which, te many cases, is incomplete, hard to go after and usually lacking knot.js examples. I did it for you! Te knot. You’re welcome.
They are (usually) swifter. Gegevens is sent to the client spil its received, frente a a poll-and-diff treatment which requires regular polling intervals. This can mean the difference inbetween a onveranderlijk 10k/s stream contra a sporadic 3k/s steam. Sites that poll many exchanges regularly increase bandwith use based on polling intervals. (For example if you attempt to use BTCAverage module, and three times a 2nd, you can lightly consume 300k/s) This module with all websockets activated consumes around 3-10k/s making it possible for low-bandwith enviornments to function somewhat efficently.
The exchange’s api does not suggest the symbol via websocket or laziness. Hook it up with a PR brah, after a while one gets burnt out glazing overheen poorly written/organized API documentation, and its all subject to switch at any given uur so prepare for this to pauze.
For the most part they do not suggest a public web socket and I did not feel it nessary to reduplicate more code to create a ‘faux-socket’, spil there are many alternatives.