[zeromq-dev] Wire-format spec for zmq 3.2

DATACOM - Samuel Lucas samuellucas at datacom.ind.br
Tue Oct 23 13:38:33 CEST 2012


On 10/22/2012 11:04 PM, Pieter Hintjens wrote:
> This should be the correct document. It's possible something is
> wrongly defined. Could you provide us with a sample of the bytes
> you're seeing on the wire? Note also that if a 3.2 peer detects a 2.x
> peer it'll revert to the old protocol.
>
>

Hi,

The reversion to old protocol explain the wire format.

I run test_reqrep_tcp.cpp from tests folders from zeromq 3.2.0 and got this:

0000   01 00 01 01 21 01 31 32 33 34 35 36 37 38 41 42
0010   43 44 45 46 47 48 31 32 33 34 35 36 37 38 61 62
0020   63 64 65 66 67 68 21 00 31 32 33 34 35 36 37 38
0030   41 42 43 44 45 46 47 48 31 32 33 34 35 36 37 38
0040   61 62 63 64 65 66 67 68

The pattern sent is the 0x31-0x68 sequence. It seems it's reverting to 
the old protocol, even both peers having 3.2.

How does it detect peer as 2.x? It doesn't looks like the procedure 
'Backward Compatibility' from 15/ZMTP.

Does the reversion to the old protocol causes any side effect to the 
applications? (disable any feature/behavior/performance?)

  - Samuel





More information about the zeromq-dev mailing list