Thanks Thijs, I have created a ticket. I have solved the problem. Once I loaded my "history" in "sharedObjectSyncHandler", the "history" can be read exactly. It's not the problem of version. But I am still confused why it has to be loaded when SyncEvent.SYNC is occurred. Is there any other event which could be used to load the "history"?
Regards, Sand ----- Original Message ----- From: Thijs Triemstra | Collab To: [email protected] Sent: Thursday, March 08, 2007 3:52 PM Subject: Re: [Red5] How to persist the sharedobject that it will notbedestroyed after I reconnect to it? Ok, give it a try with the newest version (0.6 RC2) that you can download from http://osflash.org/red5/06rc2 before you create a ticket. Thijs Op 8-mrt-2007, om 7:54 heeft wishsand((TOM)) het volgende geschreven: Red5 0.5-final is my current Red5 server version.  Thanks! Sand ----- Original Message ----- From: Thijs Triemstra | Collab To: [email protected] Sent: Thursday, March 08, 2007 7:07 AM Subject: Re: [Red5] How to persist the sharedobject that it will not bedestroyed after I reconnect to it? What version of Red5 are you using? If it's 0.6 RC2 or newer, please create a ticket on http://jira.red5.org Thijs Op 7-mrt-2007, om 9:10 heeft wishsand((TOM)) het volgende geschreven: Dear folks: Each time I getRemote, the sharedobject is renewed and I can't read the "history" from it. //The code is: soChat = SharedObject.getRemote( "ChatHistory", nc.uri, true ); soChat.addEventListener( NetStatusEvent.NET_STATUS, netStatusHandler ); soChat.addEventListener( AsyncErrorEvent.ASYNC_ERROR, asyncErrorHandler ); soChat.addEventListener( SyncEvent.SYNC, sharedObjectSyncHandler ); soChat.client = this; soChat.connect(nc); txtChatBox.text=String(soChat.data.history); //When I send the msg, the "history" is set. It should have been stored in the sharedobject and have been read once more. However, it isn't. soChat.size is always 0 when reconnect.  What's wrong with it?  Thanks! Sand  _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org -------------------------------------------------------------------------- _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org ------------------------------------------------------------------------------ _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
