Tweet

Since the biggest barrier to on-time delivery was the user interface, Cliff Hall, Futurescale Chief Architect, was brought in and delivered, according to Brian, “…a polished, ahead of schedule component that our end-users were ecstatic for. Customers with a wide base of experience with diverse CDL terminals have said that Cliff’s user interface is the best looking, most intuitive interface they have ever used on such a device. Additionally, using WebORB allowed us to quickly tie the backend systems together to provide a single view of a complex set of equipment.” According to Cliff, “Although there was much praise from the end users for the Flex GUI component, the solid WebORB backend was crucial to the overall success of tying the user interface into the complex array of hardware and software subsystems that were involved.”

Avtec Systems

Avtec builds advanced systems for unbounded data communications.  Developed over a quarter-century of commitment to the aerospace, telecommunications and defense industries, Avtec's enabling technology powers fast, reliable data flow across boundaries and through the most challenging environments. www.avtec.com

Futurescale

Futurescale offers architectural guidance and development expertise to aid in the implementation of Rich Internet Applications; specifically using the PureMVC framework for the Adobe Flash Platform. www.futurescale.com

Why do my RTMP connections in .NET keep closing or timing out?

There could be a couple reasons for connections timing out, which include:

1. IIS Idle Timeout Settings
2. RTMP Server is Reset

Idle Timeout Settings

In the performance tab of the properties where the WebORB application pool resides, there is a setting for idle timeout.  The default is 20 minutes.  Verify the timing of your timeouts.  If it is 20 minutes, this could be the problem.  You can modify that setting or completely disable it.  

Alternatively, you should consider a connection pinging strategy. A connection that has no traffic may be considered to be idle and thus inadvertently dropped. WebORB for .NET provides API to periodically ping incoming connections. The API serves two purposes: create light traffic to avoid connection termination and determine if a particular connection is a ghost. A ghost connection may occur if the user on the client-side has navigated away from the page with the client app, but the browser has not fully terminated the connection. To use the API invoke the “scheduleGhostConnectionCleanup()” method from the “appStarted” callback in your messaging application handler:

        public override bool appStart( IScope app )
        {
            scheduleGhostConnectionsCleanup();
            return base.appStart( app );
        }

RTMP Server is Reset

This happens anytime a file is modified or copied to the /bin directory and also when specific disconnect criteria is met in the AppPool.  You can create client code that reacts to disconnect conditions by attempting to reconnect the client, allowing the client to persist the connection even though the RTMP server is reset.  Alternatively, you could host the RTMP server for .NET in Standalone mode.  (Requires Enterprise Edition.)