[Red5] Sending data(byte arrays) to multiple clients using remote shared objects

[Christopher Walzl]

Hi All,

I'm using remote shared objects to send a lot of data to multiple  
clients.  I've rewritten some code I had originally implemented in a  
SOAP web service, thinking Red5 would make things simpler, and it  
would be able to send the data more quickly and efficiently(less  
overhead than a SOAP message I think).  However, I've been having some  
serious latency issues with my red5 implementation using shared  
objects. I've got a few questions related to how all of this works  
under the hood. If there is any documentation out there that goes over  
this, please let me know! :-)  I've started looking over the code, but  
I'd be grateful for any help that y'all could give!

Question 1: How does the event/data queuing work?  Is there a way to  
disable queuing? For example, if a client has not yet received the  
data for an updated key-value pair in the shared object, and that  
entry has already been overwritten, I'd like the client to receive the  
latest entry and skip the previous entry.

Question 2: Possibly related to the first question...when a client  
updates a shared object, is that data pushed back out to the other  
clients as it's received by the server, bit by bit? Otherwise it must  
wait until the entire message is received before it forwards on the  
data to the other clients? Any ideas?

Question 3: I thought I knew the answer to this, but just want to  
verify... When I update a key/value pair on a remote shared object, is  
it true that only the updated key/value data is sent out to the  
clients who are listening to this remote shared object?  The reason I  
ask, is because it appears that my bandwidth utilization is higher  
than I would have expected.

Thanks!

Chris Walzl
cwalzl at gmail.com
(972) 974-6728

Sent from my MacBook Pro