Fastream Technologies wrote: > Here is some more information about the bug: The onheaderend (which > is not demoed in the demo) is called twice: once with LastResponse = > "0" and the second time with the correct data. The onheaderdata's are > called after the first onheaderend. The bug is in there!
Sounds like these junk bytes are received very late when the subsequent GET has been issued yet. Are you using async methods? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
