Subject | Re: [Firebird-Architect] Vulcan services part II |
---|---|
Author | Arno Brinkman |
Post date | 2006-05-11T11:00:34Z |
Hi,
them it becomes the services module itselfs. Which would be wrong IMO.
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database developer support:
http://www.databasedevelopmentforum.com
Firebird open source database (based on IB-OE) with many SQL-99 features:
http://www.firebirdsql.org
http://www.firebirdsql.info
Support list for Interbase and Firebird users:
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep:
news://newsgroups.firebirdsql.info
>>Backwards compatibility of "isc_info_svc_svr_db_info" info item in theY-valve doesn't know anything about the service info-items and when you let the Y-valve parse the info-items and handle
>>service.
>
> 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.
them it becomes the services module itselfs. Which would be wrong IMO.
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database developer support:
http://www.databasedevelopmentforum.com
Firebird open source database (based on IB-OE) with many SQL-99 features:
http://www.firebirdsql.org
http://www.firebirdsql.info
Support list for Interbase and Firebird users:
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep:
news://newsgroups.firebirdsql.info