|
Title: does MtGox's streaming API update more quickly than polling via HTTP? Post by: eldentyrell on January 29, 2012, 04:38:03 PM MtGox's API documentation says that all data, including market depth, is cached every 10 seconds. This means that you can't find out about changes to the market depth more often than that.
They also have a socket.io API documented here: https://en.bitcoin.it/wiki/MtGox/API#Streaming_API Does the socket.io API only return results when the cache is updated (in which case there's really no advantage to using it unless you're writing code stuck in a browser), or does the socket.io API return order book changes more-or-less as they happen? Thanks, Title: Re: does MtGox's streaming API update more quickly than polling via HTTP? Post by: Mt.Gox Support on January 31, 2012, 01:59:32 AM MtGox's API documentation says that all data, including market depth, is cached every 10 seconds. This means that you can't find out about changes to the market depth more often than that. They also have a socket.io API documented here: https://en.bitcoin.it/wiki/MtGox/API#Streaming_API Does the socket.io API only return results when the cache is updated (in which case there's really no advantage to using it unless you're writing code stuck in a browser), or does the socket.io API return order book changes more-or-less as they happen? Thanks, Hi. Socket.io is realtime, but still under Beta explaining some of the problem you may have. However we are working on this and hope to offer a more "stable" solution. Title: Re: does MtGox's streaming API update more quickly than polling via HTTP? Post by: eldentyrell on February 02, 2012, 12:34:05 AM Hi. Socket.io is realtime, but still under Beta explaining some of the problem you may have. However we are working on this and hope to offer a more "stable" solution. Okay. Could you tell us what "error code #1" means? At least two of us are encountering it in this thread: https://bitcointalk.org/index.php?topic=14412.100 I understand that the socket.io API has been "beta" for three months now, but since it is the only real-time API (the HTTP API is on a 10-second delay) that puts some traders at a significant disadvantage relative to others. |