[Red5devs] SharedObject design question
contact at valentin-manthei.de
Tue Sep 16 04:21:22 PDT 2008
Hi out there,
I currently run a webcam chat community with advanced features.
Users broadcasting their webcams have a list of viewers to control the
access to their webcam, kick a viewer from it etc.
This list is stored in just one SharedObject with the following layout:
[user1] => [viewer1, viewer2, viewer3]
[user2] => [viewer1, viewer4]
This works fine, but in fact with every update of the viewerlist every
broadcasting user gets information about the changes (and in most cases
this information is not relevant for the target, because it is
subscribed by every user).
Would it be better to create a SharedObject for every broadcaster?
That'd be up to 150 SOs at a time.
Is Red5 able to handle a large amount of SOs? Will that probably be more
efficient than using one huge HashMap for everything? Is an increase of
performance to expect?
It is a lot ofwork to implement the SharedObjects this way, so I wanted
to ask first.
Thanks for your help,
More information about the Red5devs