>Milan Babuskov wrote:
>>
>> In short: since Classic uses multiple processes all of them cannot
>> listen on the same TCP port.

At 01:32 PM 4/01/2009, Dmitry Yemanov wrote:

>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.

1. Even on an Internet connection?

2. What of an application that's designed to do event callbacks constantly (such as DML caching in IB Objects)? How could that work on Classic?

3. Is the event table inexorably anchored to one port or can it be made so that the auxiliary port # can be tied to the PID?

./heLen