|
Hi, We have been seeing some strange effects sending simple data over NetConnection objects. We have been using them to send and receive data simultaneously. Our main test is sending 200Kb packets to the client from the server as frequently as red5 can process them (the server is just generating messages and sending them in an infinite loop), and every 100th message received the client sends a request to the server (the server does nothing with the request). After no specific time period the client disconnects. Sometimes it produces the following error, however most of the time it simply crashes: asyncErrorEventHandler: [AsyncErrorEvent type="asyncError" bubbles=false cancelable=false eventPhase=2 text="Error #2095: flash.net.NetConnection was unable to invoke callback notification." error=ArgumentError: Error #1063: Argument count mismatch on main/notification(). Expected 3, got 1.] If we use a second connection to send the requests to the server from the client then the system doesn't crash (or at least I have been able to leave it for half an hour and it continues to process). It seems as though the NetConnection object on the client cannot handle incoming and outgoing messages simultaneously, or the same may be true of the Red5 connection. Has anyone experienced this kind of problem before? Best regards, Tom Willliams --
Thomas Williams |
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
