>> I obtained a different answer depending on the URL call, and if I invoke the >> server from 10.5.36.50:4000 I receive an invalid XML string. For example: >> >> FROM HTTP://10.5.36.50:4000 (Invalid xml string) >> >> 391 // This number seems to be a random one > > This looks like chunked transfer encoding to me. This is part of the > HTTP 1.1 spec in which the server sends the number of bytes in a > chunk, followed by the chunk itself. You might want to check the > headers if you can (with something like "curl -v") to see if this is > indeed the case. If the client says that it's HTTP 1.1 it should know > how to deal with chunked transfer encoding. > >> 1 >> � > > This, however, looks odd. I'm not sure what that straggler byte is, > and that could be why the XML document is invalid, although it looks > like you also are receiving it from localhost below.
It is probably the size of the chunk as Joe pointed out. The strange byte is 0xff which beagled sends at the end of each "message" - it is used in the client javascript code to split byte streams into meaningful segments. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user _______________________________________________ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
