[Freeswitch-dev] event socket protocol
Hi, I played around a little with event socket and found that it send out the event like this: Content-Length: 1057 Content-Type: text/event-xml \n <event> ... </event>\n Content-Length: 1057 Content-Type: text/event-xml \n <event> ... So my question is wouldnt it be better to separate the event body with a \n too from the next header, just like between the header and the body, so it would be easier to parse? Regards, Csaba Zelei
The best explanation of this is: http://lists.freeswitch.org/pipermail/freeswitch-dev/2008-June/001136.html Mike On Jul 22, 2008, at 6:40 AM, Csaba Zelei wrote:
Hi,
I played around a little with event socket and found that it send out the event like this:
Content-Length: 1057 Content-Type: text/event-xml \n <event> ... </event>\n Content-Length: 1057 Content-Type: text/event-xml \n <event> ...
So my question is wouldnt it be better to separate the event body with a \n too from the next header, just like between the header and the body, so it would be easier to parse?
Regards,
Csaba Zelei
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (2)
-
Csaba Zelei
-
Michael Jerris