Dmitry Yemanov wrote:

> Milan Babuskov wrote:
>> In short: since Classic uses multiple processes all of them cannot
>> listen on the same TCP port.
>
> They cannot simultaneously, but why couldn't they subsequently? The
> event port is expected to be in the listening state for just a few
> milliseconds.

I was only explaining how Classic works currently (at least, how I
understand it works, and I have tested it to make sure). As soon as the
application requests to 'listen' to events, a secondary connection is
established on a _random_ port. You cannot NAT/forward random ports
through a firewall when you don't know which they are.

Of course, there is room to improve this in future FB versions.

P.S. I have tested with 1.5, 2.0 and 2.1. Has there been any improvement
in 2.5 maybe?

--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com