Subject Re: [Firebird-Architect] Vulcan services part II
Author Dimitry Sibiryakov
On 11 May 2006 at 10:30, Dmitry Yemanov wrote:

>> How can they know it?
>
>It's up to them. For example, currently there's a global active
>databases list protected by a mutex.

That's why I started to complain in this thread. Engine must have
as little global things as possible. What if during development of
the next engine version everybody forget to change name of this
global area? Wouldn't it be shared between two different engines?..
Besides, there are things that Y-valve can count itself without
bothering engines: it has full information about connections,
transactions, queries and so on.

>> What's the purpose of this last trip? Why Y-
>> valve can't return the results to user immediatelly after merging?
>
>Because Y-valve should not implement SAPI :-)

But it should implement fb_engine_info() call which has no
considerable differences from SAPI.

>And because the call can
>be a remote one.

Do you mean that fb_engine_info() can be called from remote site?
Just some minutes back you stated the opposite.

--
SY, Dimitry Sibiryakov.