|Re: [firebird-support] Any news regarding SuperClassic and
>Helen Borrie wrote:At 02:16 PM 4/01/2009, Dmitry Yemanov wrote:
>> 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?
>The event table has nothing to do with ports, they're layeredDmitry, Process X, a Classic instance, signals it is listening for an event. The server side of the process creates the event table and starts broadcasting on port 12345...
>separately. I seem to get your line of thinking, but I'm afraid this
>doesn't fit the architecture.
Then, Process Y signals it is listening for the same event. Now, its event callback will be delivered from the same aux port?
So what I'm asking is - does each Classic process check for the existence of the events table? i.e. the existence of the events table is independent of any particular Classic process? How does Process Y know which port to broadcast from?