Navigation:  Messaging and Streaming > RTMP Messaging >

Messaging Application

Previous pageReturn to chapter overviewNext page

A messaging application is a logical unit combining the following elements:

 

1.Custom application code - this is the code working with client connections, processing server-side and client-side events and enforcing business logic.
2.Video streams - WebORB automatically supports live or recorded stream broadcast, it can provide server-initiated streaming and record streams published by clients. Streams created and managed within application scope.
3.Remote Shared objects - WebORB supports Remote Shared Object (RSO) API enabling clients exchange data with each other or with the server. RSOs created and managed within the application scope.

Real-time messaging applications must be identified by a directory under the /Applications folder located in the root of a WebORB-enabled ASP.NET application. For example, the following structure creates two applications MyVideoApp and SharedObjectsApp:

 

WebORB version 3:

Inetpub
  +-wwwroot
      +-weborb30
           +-Applications
                 +-MyVideoApp
                 +-SharedObjectsApp

WebORB version 4:

Program Files
  +-Weborb for .NET
      +-[WEBORB VERSION FOLDER]
         +-Applications
              +-MyVideoApp
              +-SharedObjectsApp

 

To connect to a messaging application from a Flash/Flex client, use the application name in the NetConnection.connect method call as shown below:

private var nc:NetConnection;
 
public function establishConnection():void
{
 nc = new NetConnection();
 nc.objectEncoding = ObjectEncoding.AMF0;
 var uri:String = "rtmp://localhost:2037/SharedObjectsApp";
 nc.connect( uri );
}

 
Flex clients can dynamically determine the base URL (hostname and port) using the following API:

var uri:String = ServerConfig.getChannel( "weborb-rtmp" ).endpoint;