Lines Matching refs:block

30 preceding text line, the exact length of the data block being
36 data from a server, it must use the length of the data block (which it
37 will be provided with) to determine where the data block ends, and not
38 the fact that \r\n follows the end of the data block, even though it
58 key. The client sends a command line, and then a data block; after
67 data block with the item's data; this continues until the server
251 - <bytes> is the number of bytes in the data block to follow, *not*
253   it's followed by an empty data block).
265 After this line, the client sends the data block:
267 <data block>\r\n
269 - <data block> is a chunk of arbitrary 8-bit data of length <bytes>
272 After sending the command line and the data block the client awaits
299 which is received as a text line followed by a data block. After all
309 <data block>\r\n
315 - <bytes> is the length of the data block to follow, *not* including
321 - <data block> is the data for this item.
439 which is received as a text line followed by a data block. After all
449 <data block>\r\n
455 - <bytes> is the length of the data block to follow, *not* including
461 - <data block> is the data for this item.
509 text line followed by an optional data block.
520 <data block>\r\n
522 - <size> is the size of <data block> in bytes, minus the \r\n
527 - <data block> is the data for this item. Note that the data block is
554 - v: return item value in <data block>
591 long this can generate a lot of traffic, especially if the data block is very
617 - v: return item value in <data block>
619 The data block for a metaget response is optional, requiring this flag to be
663 the item can use the existing data block (if valid or stale), retry, wait, or
701 After this line, the client sends the data block:
703 <data block>\r\n
705 - <data block> is a chunk of arbitrary 8-bit data of length supplied by an 'S'
709 After sending the command line and the data block the client awaits
1664 This command does not block the server.