2011/3/22 Anthony Minessale <anthony.minessale@gmail.com>:
this is an encapsulated event inside a container event.
if you were framing this on the wire you would read the headers (everything up to the gap) the content-length of 625 tells you to read exactly that many bytes and content type text/event-plain
now when you read 625 bytes you can continue to read on the wire for a new event. Meanwhile you url decode that payload and you have another event who also has a payload of 41 bytes. Now you can read these 41 bytes to get the payload which is the exact size of the message contained in the event.
Ok, understood. I still think it's a bit strange but I understand.
None of this matters to you if you use the ESL lib supplied with FS to read events into a scripting language.
For now I just want to fully understand the protocol. I will use some existing erver library (Ruby library) for Outbound Listener, or maybe create my own one. Thanks a lot for your explanation. -- Iñaki Baz Castillo <ibc@aliax.net>