Subject Re: [Firebird-Architect] Vulcan services part II
Author Arno Brinkman

>>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.

>>> 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.

Yes, but it finally ends by the provider that correctly validates the isc_service_attach() call and that is currently
the services provider.

> 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

Arno Brinkman

General database developer support:

Firebird open source database (based on IB-OE) with many SQL-99 features:

Support list for Interbase and Firebird users:

Nederlandse firebird nieuwsgroep: