Hi Muriel,
Since I'm only using FMS right now I don't know what happens when you
call removeAttribute(). I assume it deletes the slot in the so and that
in turn causes another update. So for every client initiatived update
you now have two. Is that how it works in Red5? At any rate if you are
not keeping the information in the shared object's slots then why not
use so.send() to broadcast the information instead of putting it in a
slot? so.send() may be better than nc.call.
Yours truly,
-Brian
muriel bowie wrote:
> Hi there,
>
> thanks to all of you for the discussion. We are actually going to be
> stress testing an application for which we will implement two
> versions, one with RSO and one with method calls some time in the next
> two weeks. I'll be posting the results if anyone is interested.
>
> @Brian: with "as the Shared Objects are emptied after a message has been
> received" I mean a call to so.removeAttribute("attribute name")
>
> @Red5 team: good luck with your presentation. I am really looking
> forward to that new release!
>
> Muriel
>
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Red5 mailing list
>[email protected]
>http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
--
______________________________________________________________________
Brian Lesser
Assistant Director, Application Development and Integration
Computing and Communications Services
Ryerson University
350 Victoria St.
Toronto, Ontario Phone: (416) 979-5000 ext. 6835
M5B 2K3 Fax: (416) 979-5220
Office: POD?? E-mail: [EMAIL PROTECTED]
(Enter through LB99) Web: http://www.ryerson.ca/~blesser
______________________________________________________________________
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
