slazarov
commented
5 years ago To be honest I would use the api to check for new markets since the idea of the socket is to get you live streaming data and it’s not like bittrex publishes new markets every other second.
Obviously when it does, the socket will be faster but the speed increase would be marginal. So it’s up to you.
On Nov 20, 2018 at 5:26 pm, <lampardlb (mailto:notifications@github.com)> wrote:
Hi, I'm not familiar with websocket but to my understanding it's a real-time push notification of market data, right, so would you say it's a more efficient way to get notified when a new coin is listed (= a new market is created), compared to, say, calling the REST API after a fix interval? I've followed your tutorials and found the push information from subscribe_to_summary_deltas quite messy. Could you kindly advise whether it's practical or not please? Thanks.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (https://github.com/slazarov/python-bittrex-websocket/issues/83), or mute the thread (https://github.com/notifications/unsubscribe-auth/AbVUG5ckUXkqxh76YqPtnA8lPBJEXWebks5uxB8TgaJpZM4YrVgi).
lampardlamps
Hi, I'm not familiar with websocket but to my understanding it's a real-time push notification of market data, right? So would you say it's a more efficient way to get notified when a new coin is listed (= a new market is created), compared to, say, calling the REST API after a fix interval? I've followed your tutorials and found the push information from
subscribe_to_summary_deltasquite messy. Could you kindly advise whether it's practical or not please? Thanks.