Your best bet to keep it trivial would be configure server with multiple addresses and put multiple instances of the server on different IP - one for HTTP/AMF on 80, the second with RTMP on 80.
If you must keep remoting(AMF) and messaging(RTMP) on the same server, the best solution is to run AMF on the top of the RTMP -requires some custom components - you are getting better manageability and QoS, not to mention client RPC and other layers you can build in the communication stack for your application. That is usually reasonably small project and provides extremely robust solution. Crude public description of the approach is here http://flexblog.faratasystems.com/?p=215 and here is http://flexblog.faratasystems.com/?p=232 description why you might want it. Regards, Anatole Tartakovsky Farata Systems On 10/16/07, Battershall, Jeff <[EMAIL PROTECTED]> wrote: > > I'm trying to get my wits around RTMP and any firewall issues that may > exist with it. I understand that Adobe's RTMP implementation uses http > tunneling - does this mean that the firewall doesn't in fact have to > have port 2048 open? That the rtmp requests in fact come over on port 80 > in the http headers? > > Just trying to understand - any explanation appreciated. > > Jeff Battershall > Application Architect > Dow Jones Indexes > [EMAIL PROTECTED] <jeff.battershall%40dowjones.com> > (609) 520-5637 (p) > (484) 477-9900 (c) > >
