<p>You would expect websockets to be more real-time because it is designed as an upgrade to HTTP to enable live streaming and real-time services.</p>

CC BY-SA 3.0
2013-11-30T02:44:39.067Z
Thanks. Do you have any direct experience of this?
Graeme
CC BY-SA 3.0
2013-11-29T16:45:36.050Z
2013-11-29T16:45:36.050Z
Bitlab.co
<p>MtGox currently offers both a websockets and HTTP API services. According to the documentation the HTTP service caches prices for 10sec but there is no clarification (that I can find) that details the real-time guarantees of the streaming services?</p>

<p>Which would be expected to be closest to real-time?</p>

<mtgox>
MtGox websockets vs HTTP - which is more real-time?
Graeme
# MtGox websockets vs HTTP - which is more real-time?

(Asked by: username_0 on 2013-11-29)

MtGox currently offers both a websockets and HTTP API services. According to the documentation the HTTP service caches prices for 10sec but there is no clarification (that I can find) that details the real-time guarantees of the streaming services?

Which would be expected to be closest to real-time?

**Tags:** mtgox


---

## 1 answers

### Answer by username_1 on 2013-11-29. Score: 1

You would expect websockets to be more real-time because it is designed as an upgrade to HTTP to enable live streaming and real-time services.

> **Comments:**
> **username_0**: Thanks. Do you have any direct experience of this?  

---

