Hello,
i am new to red5 but maybe this could help. From the API documentation
about the createSharedObject resident in the ApplicationAdapter Class:
Creates a new shared object for given scope. Server-side shared
objects(also known as Remote SO) are special kind of objects those
variable are
synchronized between clients. To get an instance of RSO at client-side, use
SharedObject.getRemote(). SharedObjects can be persistent and transient.
Persistent RSO are statuful, i.e. store their data between sessions. If you
need to store some data on server while clients go back and forth use
persistent SO (just use true ), otherwise perfer usage of transient for
extra performance.
Parameters:
scope Scope that shared object belongs to
name Name of SharedObject
persistent Whether SharedObject instance should be persistent or not
Returns:
true if SO was created, false otherwise
Hope it helps!
Regards,
Diego.
On 7/6/07, Nauman Nasir <[EMAIL PROTECTED]> wrote:
Hello!
I studied the simple chat application, in which the shared object is
actually not at the server. Every client has an object that changes its
value when any of the client makes some change in its object, so we can
say
that this object is shared..
now i want to make an object on server side, so that each client reads and
writes the object on the server, in this way i can have a real shared
object.......... Please help me to do that.
i have following softwares on my machine:
1) RED 5 server...
2) NetBeans (to compile the classes).
3) flash 8
--
*************************************************
The life is too short to Love.
I donot know how people manage to hate
*************************************************
Ch. Nauman Bin Nasir
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
--
saludos.
diegoH.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
