Subject Re: [Firebird-Architect] Vulcan services part II
Author Dimitry Sibiryakov
On 11 May 2006 at 9:22, Arno Brinkman wrote:

>> Note: not all services but only those that cannot be served by
>> providers.
>I think that are a lot.

Name first... five.

>> For this purpose we already have isc_database_info() which has
>> dbHandle.
>Yes, a somewhat equal call, but database_info returns only information
>about the specified database. fb_engine_info returns information over
>all active databases.

But then why to give it a dbHandle?

>> For this purpose we already have isc_service_attach() which has
>> "service" param that holds servername (and engine name?).
>But it attaches to a services provider and not engine.

Wrong. It attaches to Y-valve (as all other calls do). Where it
will be redirected to is a matter of config and Y-valve logic.

>> Not so complex because all things you are thinking about must be
>> served not in dispatcher but in providers. Dispatcher is for global
>> things only.
>That's what currently is already the situation. The only missing thing
>is the engine information, that what we're discussing about?

We are discussing about which provider must provide information
about engine. I think that it must be the engine because only engine
has all necessary information.

SY, Dimitry Sibiryakov.