Subject Re: [Firebird-Architect] Vulcan services part II
Author Alex Peshkov
Dimitry Sibiryakov wrote:
> On 11 May 2006 at 11:43, Dmitry Yemanov wrote:
>>But not about databases or users. The info requests cannot be handled
>>only by the Y-valve.
> Right. These requests can be handled only by all providers
> together.

Appears I'm a bit late in this discussion, but this is suspicious for
me. In pre-vulcan firebird we did had single local provider (I hope
noone suggests to try to get mentioned information from remote/gateway
providers - this may lead to infinite recursion), and therefore it was
not a question: databases/users, opened by server or by provider.

With vulcan there is such question. And I'm not so sure that all server,
not provider information, should be collected. Providers have separate
lock managers, they may be reset separately - why mix ODS10 and ODS11
databases? The other side is that in case when we suppose to restart
service we need information about all providers: are there active
connections or not (that's not good to restart service even if it has
some gateway-only connections). But *that* data may be requested
directly from Y-valve - it can track all opened handles in
provider-independent way.

Sorry if I've repeated some things, already discussed.