I believe SharedObject's are supposed to send only a event.info.code = success to the sender. Additionally if you change a sharedobject's data to what it already contains, no sync happens which is intended. I'll have to do some checks though.
On 8/14/07, Martijn van Beek <[EMAIL PROTECTED]> wrote: > > Somehow R5 is behaving strangely with SharedObject in my application. > According to my knowledge a sharedObject broadcasts and sends an update to > every client disregarding the fact who is the sender (My FMS application I > made last year behaves that way). > > R5 doesn't do this, is this on purpose? I run 0.6.2 on Ubuntu with Java > 1.6. > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > > -- Dominick Accattato, CTO Infrared5 Inc. www.newviewnetworks.com
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
