Hi,

I have cleaned up the tutorial code examples I had posted here earlier (
http://jwamicha.wordpress.com/2007/01/29/create-a-new-java-red5-application/)
and tested them to ensure they work.

The following has now been added to the tutorial and sample code. Use
Joachim's Migration guide (
http://www.joachim-bauch.de/tutorials/red5/MigrationGuide.txt) as a
reference:

1. Create a red5 server transient shared object. Get its value from the flex
client.
2. Create a red5 server persistent shared object. Get its value from the
flex client.
3. Create a red5 server transient shared object. Change its value from the
flex client.
4. Create a red5 server persistent shared object. Change its value from the
flex client.
5. Flex client send an object (message) to red5 and store it in red5 server
transient shared object.
5. Flex client send an object (message) to red5 and store it in red5 server
persitent shared object.
6. Trigger Transient SharedObject Listener onSharedObjectUpdate method,
whether it is the red5 application code or the flex client that has changed
the shared object's value.
6. Trigger Persistent SharedObject Listener onSharedObjectUpdate method,
whether it is the red5 application code or the flex client that has changed
the shared object's value.

What is currently remaining is:
1. Registering a shared object handler for a transient shared object and
ensuring the flex client can call red5 server methods using
getremote_so.send("handler", "args"). Providing flex client onsync for this
transient shared object.
2. Registering a shared object handler for a persitent shared object and
ensuring the flex client can call red5 server methods using
getremote_so.send("handler", "args"). Providing flex client onsync for this
persitent shared object.

Hopefully this last part of the tutorial will be ready in the next few days.

--
C is forever.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to