As you build video applications, it is important to learn the art of managing connections and streams. In a networked environment, a connection attempt might fail for any of these reasons:

• Any section of the network between client and server might be down.
• The URI to which the client attempts to connect is incorrect.
• The application instance does not exist on the server.
• The server is down or busy.
• The maximum number of clients or maximum bandwidth threshold may have been exceeded.

If a connection is established successfully, you can then create a NetStream object and stream video. However, the stream might encounter problems. You might need to monitor the current frame rate, watch for buffer empty messages, downsample video and seek to the point of failure, or handle a stream that is not found.

To be resilient, your application needs to listen for and handle netStatus events that affect connections and streams. As you test and run your application, you can also use the Administration Console to troubleshoot various connection and stream events.