MACROMEDIA FLASH MEDIA SERVER 2-DEVELOPING MEDIA, Руководство по разработке, Страница: 40 / 114

40 Using Media Classes
You can use Macromedia Flash Remoting with the Flash Media Server to communicate with
application servers such as Macromedia ColdFusion, .NET, and J2EE servers. For more
information, see the Flash Remoting information on the Macromedia website at
www.macromedia.com/go/flashremoting .
SharedObject class Server-side shared objects let you communicate with client-side shared
objects and with objects on other Flash Media Servers. For more information about server-
side shared objects, see
“Understanding shared objects” on page 41 .
Stream class. The server-side Stream class lets you handle each stream in a Flash Media
Server application. Flash Media Server automatically creates a Stream object when the
NetStream.play()
or
NetStream.publish()
method is called in a client-side script. You
can also create a stream in server-side ActionScript by calling the
Stream.get()
method. A
user can access multiple streams at the same time, and there can be many Stream objects active
at the same time.
WebService class The server-side WebService class lets you to create and access a WSDL/
SOAP web service. The following server-side classes are used in tandem with the WebService
class: the Log class, the SOAPFault class, and the SOAPCall class.
XML class
The server-side XML class lets you load, parse, send, build, and manipulate
XML document trees.
XMLSocket class The server-side XMLSocket class implements client sockets that let the
Flash Player communicate with a server identified by an IP address or domain name.
XMLStreams class
The server-side XMLStreams class is a variation of the XMLSocket
class—it has all the same methods, properties, and events, but it transmits and receives data in
fragments.
About client-server communication
The following “object pairs” represent the potential connections you can establish between
client-side and server-side objects. For example, when a client-side NetConnection object
connects to the server, a server-side Client object is created; this Client object can then call
methods of its NetConnection object counterpart.
The following table shows the client-side and server-side objects that are associated with
each other.
Client-side object Corresponding server-side object
my_nc
(NetConnection object)
my_client
(Client object or
application.clients
object)
my_ns
(NetStream object)
my_server_stream
(Stream object)
my_so
(remote shared object)
my_server_so
(server-side shared object)