Subject | Re: [Firebird-Architect] Vulcan services part II |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-05-11T11:44:56Z |
On 11 May 2006 at 12:27, Arno Brinkman wrote:
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.
--
SY, Dimitry Sibiryakov.
>>>Yes, and were discussing which method to use, but for backwardsI'm sorry, but there is no relation between backwards compatibility
>>>compatibilty this must be supported inside services provider.
>
>Backwards compatibility of "isc_info_svc_svr_db_info" info item in the
>service.
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.
--
SY, Dimitry Sibiryakov.