Evert, --Ports can't be instable. The difference between port 80 and 1935 is the 16 bit integer value.. Nothing else is involved here.. ----
I meant his system doesn't handle rtmp in a stable manner. The connection drops out for some reason and red5 dist doesn't have a "fallback mechanism" from rtmp port 1935 to 80 or 443 like fms or wowza's mechanism. Regards, Ben Wade -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evert | Rooftop Sent: Thursday, August 09, 2007 12:01 PM To: [email protected] Subject: Re: [Red5] instable port correction Ben Wade wrote: > > It seems that Red5 does not automatically detect working ports and correct > it like FMS and wowza do (which he can stream from). Here's a scenario. If > port 1935 is not stable (for whatever reason) then port 80 or port 443 would > automatically be used and swapped if need be on the fly. Ports can't be instable. The difference between port 80 and 1935 is the 16 bit integer value.. Nothing else is involved here.. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
