Flash Media Server |
|||
| Developing Media Applications > Using Media Classes > About Flash Media Server classes > About Server-side classes | |||
These classes are used only in server-side ActionScript. For more information about these classes, see the Server-Side Media ActionScript Language Reference.
Application class The server-side Application class lets you create objects that contain information about a Flash Media Server application instance; the object lasts until the application instance is unloaded. The Application class lets you accept and reject client connection attempts, register and unregister classes and proxies, and create functions that are invoked when an application starts or stops, or when a client connects or disconnects.
Client class The server-side Client class lets you create objects that represent each user's connection to a Flash Media Server application instance. A Client object can receive messages sent by a client-side NetConnection.call() command, and can invoke methods of the client-side NetConnection object. You can use the properties of a Client object to determine the version, platform, and IP address of each client. Using the Client class, you can also set individual read and write permissions of various application resources such as Stream objects and SharedObject objects. For more information, see Implementing dynamic access control.
File class The server-side File class lets applications write to the server's file system.
LoadVars class The server-side LoadVars class lets you to load variables into a server-side script from a remote or local location.
NetConnection class The server-side NetConnection class lets you create a two-way connection between a Flash Media Server application instance and an application server, another Flash Media Server, or another Flash Media Server application instance on the same server. You can also use server-side NetConnection objects to create more powerful applications; for example, you could get weather information from an application server, or share an application load with other Flash Media Servers or application instances.
Using a NetConnection object, you can connect to an application server for server-to-server interactions using standard protocols (such as HTTP), or connect to another Flash Media Server for sharing audio, video, and data using the Macromedia Real-Time Messaging Protocol (RTMP).
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.
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.
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/fms/2/docs/00000047.html