[Red5] instable port correction

Thijs Triemstra | Collab lists at collab.nl
Thu Aug 9 10:53:44 PDT 2007


True, that's a client side thing but being able to run all protocols  
on all ports isn't possible with Red5 atm and that's what we're  
looking for..

Quote from Joachim in APPSERVER-124:

"The fallback from RTMP to RTPMT is done by the client, not the  
server. And of course you can setup Red5 to run on port 1935 (RTMP)  
and 80 (RTMPT). Just edit conf/red5.properties and restart the server.

What you probably want is a possibility to run all protocols on any  
port - this is an enhancement and not that easy as we have different  
networking libraries for RTMP and RTMPT (HTTP)."

Thijs

On Aug 9, 2007, at 7:38 PM, Luke Hubbard wrote:

> Isn't it client side code that is responsible for switching to run  
> over other ports.
> I don't see how this can be handled on the server since it cannot  
> control a client that is not connected.
>
> - Luke
>
> On 8/9/07, Ben Wade <bwade at allwebnow.com> wrote:
> 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: red5-bounces at osflash.org [mailto:red5-bounces at osflash.org] On  
> Behalf
> Of Evert | Rooftop
> Sent: Thursday, August 09, 2007 12:01 PM
> To: red5 at osflash.org
> 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
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
> _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>
>
> -- 
> Luke Hubbard
> codegent | coding for the people
> http://www.codegent.com
>
> NMA Top 100 Interactive Agencies - Ones to watch!
> http://www.codegent.com/top100/
>
> want to know more?
> http://www.codegent.com/showreel/
>
> This e-mail may contain information which is privileged,  
> confidential and protected from disclosure. If you are not the  
> intended recipient of this e-mail, or any part of it, please delete  
> this email and any attachments immediately on receipt. You should  
> not disclose the contents to any other person or take copies. Any  
> views expressed in this message are those of the individual sender,  
> except where the sender specifically states them to be the views of  
> codegent limited.
> _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5_osflash.org/attachments/20070809/d3e9ec08/attachment-0001.html 


More information about the Red5 mailing list