Hi Tom,
From XMLSocket docs:
* Each XML message is a complete XML document, terminated by a zero (0)
byte.
...
* Each document is terminated with a zero (0) byte. When Flash Player
receives the zero byte, it parses all the XML received since the previous
zero byte or since the connection was established if this is the first
message received.
Perhaps your server doesn't set the closing zero byte for close messages.
I had similar issue several years ago (in 2003) - solved when they set this
zero byte for each server's message.
On 5/1/07, Tom Gooding wrote:
Calling all AS2.0 developers who have experience working with XMLSocket
connections..
I've recently been seeing an odd behaviour in an app I've developed
which has a continual connection to a socket server.
The symptom I've been seeing is the connection becoming inactive, the
onClose event does not get fired, it just stops receiving XML. My
current workaround is to monitor idle time on this connection and
reconnect if a ceiling is reached. The current thinking is that this is
due to some network/firewall/environmental issue and investigation is
time-consuming, though a bug with flash has not been ruled out.
I was wondering if anyone has experienced anything similar and found the
root cause of it? Any thoughts would be greatly appreciated.
Tom
--
--
Best regards,
GregoryN
http://GOusable.com
Flash components development.
Usability services.
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
