Lines Matching full:chunk
189 <p>Information is sent in chunks. Each chunk starts with:
197 need an "error" chunk type and a handler on the server side.]
199 <p>The same chunk type may have different meanings when sent in different
207 and extensions"). Using the chunk format allows us to remain independent
210 single transmission unit. [I'm taking the multi-chunk packets into
215 compressed. Compressed chunks are written as a chunk type that
217 by the original chunk type and the uncompressed length. For zlib's deflate
218 algorithm, the chunk type is "ZLIB".
232 <p>After the JDWP handshake, the server sends a HELO chunk to the client.
239 <h4>Chunk HELO (server --> client)</h4>
246 <h4>Chunk HELO (client --> server, reply only)</h4>
274 <h4>Chunk DBGD (server --> client)</h4>
282 <h4>Chunk APNM (client --> server)</h4>
291 <h4>Chunk WAIT (client --> server)</h4>
301 chunk will be sent up at about the same time as the HELO response.
310 <h4>Chunk THEN (server --> client)</h4>
320 <h4>Chunk THCR (client --> server)</h4>
328 <h4>Chunk THDE (client --> server)</h4>
334 <h4>Chunk THST (server --> client)</h4>
346 <h4>Chunk THST (client --> server)</h4>
401 <h4>Chunk HPIF (server --> client)</h4>
414 <h4>Chunk HPIF (client --> server, reply only)</h4>
434 <h4>Chunk HPSG (server --> client)</h4>
446 <h4>Chunk NHSG (server --> client)</h4>
457 <h4>Chunk HPST/NHST (client --> server)</h4>
469 <h4>Chunk HPEN/NHEN (client --> server)</h4>
478 <h4>Chunk HPSG (client --> server)</h4>
479 <p>Heap segment data. Each chunk describes all or part of a contiguous
544 (a) the end of the chunk is reached, or (b) all allocation units have been
546 chunk is rejected.)
549 The client could send one chunk (allocSize=8, virtAddr=0x10000, offset=0,
557 <h4>Chunk HPSO (client --> server)</h4>
569 <h4>Chunk NHSG (client --> server)</h4>
570 <p>Native heap segment data. Each chunk describes all or part of a
586 The client-side chunk handlers need a common way to report simple success
589 <h4>Chunk FAIL (client --> server, reply only)</h4>
590 <p>The chunk includes a machine-readable error code and a
603 <h4>Chunk EXIT (server --> client)</h4>
610 <h4>Chunk DTRC (server --> client)</h4>
621 <h3>Chunk Handler API</h3>
624 specific chunk types. When a DDM chunk with that type arrives, the
629 and has all of the chunk handlers and registration code. It can freely
638 class Chunk {
645 <p>The chunk handlers accept and return them:
647 public Chunk handleChunk(Chunk request)
649 <p>The code is free to parse the chunk and generate a response in any
651 <p>Chunk handlers will be notified when a DDM server connects or disconnects,
667 write multiple chunks in response to a single chunk should send a null
672 <p>If a piece of code wants to send a chunk of data to the server at some
677 public static void sendChunk(Chunk chunk)
699 <p>The chunk handlers look like this:
709 <dd>The 32-bit chunk type.
