Hey, sorry missed that. So these bytes are part of the record response of this command (synch-result-content, can only be a record). And the "signature" of a record is "(record-type:byte)(cluster-id:short)(cluster-position:long)(record-version:int)(record-content:bytes)" and the short before is the "record-kind". Take a look at the record type here http://www.orientechnologies.com/docs/last/orientdb.wiki/Network-Binary-Protocol.html#supported-types
Cheers, Chris Am Dienstag, 10. Februar 2015 19:38:03 UTC+1 schrieb Philip Wernersbach: > > Christian, > > Thanks for the reply. I reread the Request section, but the bytes I'm > asking about are in the "synch-result-content" section of the > REQUEST_COMMAND command-specific reply data. > > Sincerely, > Philip Wernersbach > > On Mon, Feb 9, 2015 at 2:17 AM, Christian Kramer <[email protected] > <javascript:>> wrote: > >> Hey, >> >> take a look at the Request section of the OrientDB binary protocol part >> at the wiki >> >> >> https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#request >> >> Cheers, >> Chris >> >> Am Sonntag, 8. Februar 2015 05:07:30 UTC+1 schrieb [email protected] >> : >> >>> Can someone tell me what the unaccounted for bytes are before the Binary >>> Schemaless Serialization result below? (The unaccounted for short, byte, >>> short, long, int) The protocol command used was an idempotent >>> REQUEST_COMMAND. >>> >>> Thanks, >>> Philip Wernersbach >>> >>> 2015-02-07 16:50:24:651 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Read 39 bytes: qselect from sung_by*:1 [OChannelBinaryServer] >>> >>> 2015-02-07 16:50:24:666 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing byte (1 byte): 0 [OChannelBinaryServer] >>> >>> 2015-02-07 16:50:24:667 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing int (4 bytes): 2 [OChannelBinaryServer] >>> >>> 2015-02-07 16:50:24:670 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing byte (1 byte): 108 [OChannelBinaryServer] => synch-result-type >>> >>> 2015-02-07 16:50:24:670 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing int (4 bytes): 2 [OChannelBinaryServer] => # of records returned >>> >>> 2015-02-07 16:50:24:714 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing short (2 bytes): 0 [OChannelBinaryServer] => ??? >>> >>> 2015-02-07 16:50:24:718 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing byte (1 byte): 100 [OChannelBinaryServer] => ??? >>> >>> 2015-02-07 16:50:24:718 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing short (2 bytes): 13 [OChannelBinaryServer] => ??? >>> >>> 2015-02-07 16:50:24:719 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing long (8 bytes): 0 [OChannelBinaryServer] => ??? >>> >>> 2015-02-07 16:50:24:719 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing int (4 bytes): 3 [OChannelBinaryServer] => ??? >>> >>> 2015-02-07 16:50:24:721 INFO {db=GratefulDeadConcerts} /127.0.0.1:50985 >>> - Writing bytes (4+31=35 bytes): [0, 14, 115, 117, 110, 103, 95, 98, 121, >>> 6, 111, 117, 116, 0, 0, 0, 27, 13, 4, 105, 110, 0, 0, 0, 29, 13, 0, 18, 2, >>> 18, 16] [OChannelBinaryServer] => Binary Schemaless Serialization >>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "OrientDB" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/orient-database/i3IXXVLCyNo/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
