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

>>>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?
>Looking up the provider that is bind to the attachment.

So, fb_engine_info in this case must return information from only
one provider? What's the difference from isc_database_info()?

>> 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.
>Yes, and were discussing which method to use, but for backwards
>compatibilty this must be supported inside services provider.

Vulcan has backward comatibility? There are previous versions of
I don't understand this: "for backwards compatibilty this must be
supported inside services provider". Who cares where requested
information comes from - services provider, engine or Y-valve as long
as the information is correct.

SY, Dimitry Sibiryakov.