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

>>Backwards compatibility of "isc_info_svc_svr_db_info" info item in the
> I'm sorry, but there is no relation between backwards compatibility
> of "isc_info_svc_svr_db_info" info item and implementing it in
> separate services provider. I'd even say that separate provider is
> the worst place for it.
> On contrary, Y-valve is almost ideal one because it has full list
> of connections, including handles for each connection and can gather
> all needed information from these connections using separate
> isc_database_info(db_id) calls for each connection.

Y-valve doesn't know anything about the service info-items and when you let the Y-valve parse the info-items and handle
them it becomes the services module itselfs. Which would be wrong IMO.

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: