diff options
| author | Matthew Hodgson <matthew@matrix.org> | 2014-09-02 21:18:00 +0100 |
|---|---|---|
| committer | Matthew Hodgson <matthew@matrix.org> | 2014-09-02 23:50:40 +0100 |
| commit | 2b9afa775eabfe6cef1757ff4885fada8f41741e (patch) | |
| tree | 34aeaceeb9e4a6164054dab8ce1d1180c6886921 /docs | |
| parent | Edited room creation section to mention all the events created when the room is. (diff) | |
| download | synapse-2b9afa775eabfe6cef1757ff4885fada8f41741e.tar.xz | |
more critique
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/specification.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/specification.rst b/docs/specification.rst index 20e7a0d85f..5381e0db51 100644 --- a/docs/specification.rst +++ b/docs/specification.rst @@ -338,7 +338,8 @@ returns, an ``end`` token is included in the response. This token can be used in request to continue where the client left off. .. TODO - Do we ever return multiple events in a single request? Do we ever support streaming + Do we ever return multiple events in a single request? Don't we get lots of request + setup RTT latency if we only do one event per request? Do we ever support streaming requests? Why not websockets? When the client first logs in, they will need to initially synchronise with their home |