In doing some testing, I found that while an initial onSync happens, the data property of the SO is empty (null) until the next forced sync. Here's the trace:
(2651) newMessageHandler update: null
(6239) newMessageHandler update:
x = 316.95
y = 233
(6271) newMessageHandler update:
x = 317.95
y = 233
2651 is the connection sync, and the other 2 are when I move the ball on the other client.
I'll talk to the dev team to see if this is a bug or not
Thanks Gunther,
JG
On 4/26/06, Gunther Konig <
[EMAIL PROTECTED]> wrote:
Using the BallControl demo with 0.4, when a second client is connected
it doesn't receive the properties of the shared object. Moreover, if
it disconnects, changes the SO and then reconnects it will send the
changes to the first client. This is different than what it used to be
in 0.3, and what seems more logical. I haven't used FMS or FCS before,
but sending the entire object on connect seems logical (for chat
history lines, for example). Any idea what happened and which behavior
is correct?
Regards,
GK
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
--
John Grden - Blitz
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
