After doing some digging, I've found that the scope is persisted if you choose to store a new attribute on the object. Calling scope.setAttribute() will trigger the serialization. Hope that this helps others. I am still seeing issues with the *disconnect and *leave methods not being invoked, but the scope is not being persisted anymore. So it would seem that more digging is required to fully remedy my issues.
Carl On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
hi carl, not sure what ur problem is. However i am using Red50.6rc1 with persistence set to true and the roomDisconnect gets fired whenever the user drops a connection. sorry i am not more helpfull. -lp > Hi all: > > I am curious to understand what triggers the scope to be persisted in an > application. I am seeing a behavior that when the scope is persisted, > the > *disconnect and *leave methods are never called in my ApplicationAdapter > subclass upon client disconnection. I've created all SharedObjects with > the > persistence flag set to false. What else is there to be persisted? Any > insight is appreciated. > > Thanks. > Carl > -- > Be who you are and say what you feel, because those who mind don't matter > and those who matter don't mind. > - Dr. Seuss > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > --------------------------------- Lucio Piccoli Director Asterisk-i Pty Ltd Software Design-Develop-Deploy www.asteriski.com _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
-- Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seuss
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
