[rtmpdump] Does rtmpdump fallback to other ports?

[Stef]

On 12/08/2011 12:15 AM, Steven Penny wrote:
> On Thu, Aug 11, 2011 at 8:42 AM, Stef wrote:
>> Does RTMPdump fall back automatically to one of the other ports (80, 443) if it cannot get access to port 1935 or doesn't it do that (yet)?
> It does not do that, and I dont see any reason for it when you can
> easily change the port with -c
>
Here's a reason - and exactly what happened.

What if RTMPdump (the executable) is part of a system where another 
program calls RTMPdump?  Let's say iViewNapper or the FireFox 
extension.  In these cases, RTMPdump.exe is the backend to another 
program.  You cannot just simply try to see if the RTMPdump can open the 
file - it only returns a can or cannot response.  There's no way to know 
from that response if it was just the file is not available or if there 
was a problem opening the port.

It's not that easy for the *user* (who may be not a geek) to hack into 
the front-end program (FF extension, iViewNapper) in order to make it 
work.  RTMPdump doesn't show a message about not being able to access 
the port, nor does it return a value to suggest to the front-end program 
to use "-c".

It would be a nice, and perhaps convenient, option if RTMPdump handled a 
fall-back itself (like the Flash Player Client).

Just sayin'...

Regards,
Stefan Zakarias.