Reconnecting a broken stream

Question

In our application we stream live audio/video images of an
event and record them for later review and playback. The power
supply at our source locations is not reliable, and even with UPSs
we run into difficulties where a video stream will be disrupted.
Once we have power restored, we want to reestablish the A/V
stream from a camera and "reconnect" it to it's original, so there
is a single recorded stream for the event from that camera even
after power was lost. We also want to reestablish the video
connection in the flash players that lost the stream when the
outage occurred.
Can that be done?

Answer 1

quote:
Originally posted by:
Neeeol
I tested this idea by setting up a timer and checking
NetConnection.isConnected every 3 seconds. It kept reporting that
the connection was good even after I stopped the Flash Server. I
don't know what that means, but it wasn't what I expected.
You really checked all events like netconnection.close and
netconnection.failed ?
Livedocs
We do use the method mentioned by Jay too (by using a client-
and server-sided interval that checks the client's ping-time and
ket the client reconnect or disconnect the dirty client on the
server to maintain a clear state of all connected clients. The
events however should trigger ; they do overhere tbh.
Trace the netconnection object and pull some plugs from your
PC, switch/hub or router to simulate a faulty network connection.
Please do note that Windows detects an unplugged networkcable which
results in a "hard disconnect". If you'd setup a simple hub/switch
between your PC and your Lan you can pull the networkcable from the
hub/switch to the rest of the LAN which emulates a
connection-problem "in the middle" which cannot be detected by your
(Windows) OS.
We call this a soft disconnect and it can take 10-30 seconds
before your Flash client will notice a "disconnect" from the
server. This is all related to timeouts of tcp-packets and stuff
which is way too deep and cannot be altered anyway. You should
however understand that network-timeouts of 5 to 10 seconds CAN
happen with a heavily loaded FMS and/or congested network.