Hmm... no one has an idea?! even the developer??!! Is that the part where i have to go through all source code, not only the one form the shared object???!!!
cu nomIad On Sun, 11 Jun 2006 19:19:17 +0200, -nomIad- <[EMAIL PROTECTED]> wrote: > Hi, > > Is it possible to lock a shared object for client updates? > It would be a misapplication BUT the thing is that shared objects have a > real fast sync time with the clients. In my case i need to syncronize > values like state of user, streamname, name and icon. An easy solution > would be to sum that up in a shared Object, because all information is > public. > The problem. A shared object is accessible AND also editable by users. > Is there a simple fine secure solution with anything other than a shared > object or can i prevent the client from changing the object? > > > Ive read the sourcecode of the vidchat of red5 but want another solution > if its possible. > > mfg nomIad > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
