Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
development:realtime:draft_header_chunks [2012/01/26 11:17]
131.174.45.5 created
development:realtime:draft_header_chunks [2017/08/17 11:21] (current)
Line 1: Line 1:
-==== Draft specification ​for handling header and chunks ====+{{tag>​realtime development}} 
 + 
 +====== Suggested improvements ​for handling header and chunks ​======
  
 This is a draft for the calls involved in writing and reading header information and chunks, where the server This is a draft for the calls involved in writing and reading header information and chunks, where the server
Line 5: Line 7:
 the current header. the current header.
  
-=== PUT_HDR ===+==== PUT_HDR ​====
  
 The client would send the following structure (after the usual **version;​command;​msgsize** triple): The client would send the following structure (after the usual **version;​command;​msgsize** triple):
Line 17: Line 19:
 The server would respond with a **version;​errorcode;​msgsize=0** triple. The server would respond with a **version;​errorcode;​msgsize=0** triple.
  
-=== GET_HDR ===+==== GET_HDR ​====
  
 The client would send the triple **version;​command**=GET_HDR;​**msgsize=0**,​ and the server would respond with: The client would send the triple **version;​command**=GET_HDR;​**msgsize=0**,​ and the server would respond with:
Line 35: Line 37:
 the last call to GET_HDR. At the same time, the amount of data transmitted is very small. the last call to GET_HDR. At the same time, the amount of data transmitted is very small.
  
-=== PUT_CHUNK ===+==== PUT_CHUNK ​====
  
 With this request, a client can write a chunk to the buffer. If there already is a chunk of this type, With this request, a client can write a chunk to the buffer. If there already is a chunk of this type,
Line 49: Line 51:
 The server would respond with a **version;​errorcode;​size=0** triple. The server would respond with a **version;​errorcode;​size=0** triple.
  
-=== GET_CHUNK ===+==== GET_CHUNK ​====
  
 With this request, clients can retrieve particular chunks from the buffer. ​ With this request, clients can retrieve particular chunks from the buffer. ​
Line 58: Line 60:
 The server will respond with the usual **version;​errorcode;​msgsize** triple, plus the list of requested chunks. The server will respond with the usual **version;​errorcode;​msgsize** triple, plus the list of requested chunks.
 If **any** of the chunks the client asked for is not available, the server will only reply with an error (no chunks attached). If **any** of the chunks the client asked for is not available, the server will only reply with an error (no chunks attached).
 +
 +===== See also =====
 +  * [[draft network]]
 +  * [[draft implementation]]
 +  * [[draft header chunks]]
 +  * [[draft compatability]]
 +  * [[scratchpad]]
 +
 +