I have a couple of comments on this. First off, there is nothing to say you can't run RTMP on port 80 so if it is just a port number issue, you can get around that problem. Of course most servers will need to be listening for both RTMP and HTTP traffic so that would require more than one IP address to allow both to listen to port 80 at the same time.
I think that some folks have constraints so that they need to be running their app server behind the firewall so it is not directly exposed to clients. In many J2EE architectures, the web server sits on the DMZ and serves up static files and proxies dynamic requests to the app server tier. We do not yet have a multi-tier solution for RTMP but this is something we're looking at. As Tom mentions, we are working on support for RTMPT - the HTTP based tunneling version of the RTMP protocol. This uses the same actual server socket as RTMP but wraps RTMP traffic in HTTP requests. We detect which protocol is being used by looking at the first few bytes the client writes. You could theoretically proxy these requests using an HTTP based proxy server to keep the RTMP server behind the DMZ. RTMPT does require polling the server though so this is not as scalable as using plain old RTMP. We implemented it primarily so that clients can get real time data delivery even when their only internet connectivity is through an HTTP proxy server. Jeff -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Chiverton Sent: Wednesday, February 28, 2007 8:51 AM To: [email protected] Subject: Re: [flexcoders] FDS port in biggest disadvantage in Flex? On Wednesday 28 Feb 2007, marcel.panse wrote: > Because flex uses another port for FDS instead of 80... A lot of users > have firewalls installed and cant use ports other than 80 or have to > adjust there firewalls. I work at a company who just can't use other > ports.. I belive there was a post from Adobe asking if anyone wanted to try a new FDS/SDK that would tunnel over port 80. > Another problem is you have to specify an new port for every flex > application you host on your server. Every webapp needs its own fds > port. So you have to forward who ranges of ports in you firewalls and > systems.. You could then use a reverse web proxy to send the requests to the correct back end. -- Tom Chiverton Helping to assertively optimize edge-of-your-seat partnerships On: http://thefalken.livejournal.com **************************************************** This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links
