Subject | Re: [Firebird-Architect] Vulcan services part II |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-05-11T05:37:03Z |
On 10 May 2006 at 23:35, Arno Brinkman wrote:
providers.
dbHandle.
"service" param that holds servername (and engine name?).
served not in dispatcher but in providers. Dispatcher is for global
things only.
isc_database_info().
--
SY, Dimitry Sibiryakov.
>1) Increase subsytem with more calls, so engine can supportNote: not all services but only those that cannot be served by
>backup/restore/validate/etc...
> Dispatcher should handle the service params and implement services.
providers.
>2) Increase subsystem with fb_engine_info() method only.For this purpose we already have isc_database_info() which has
>fb_engine_info() has dbHandle so dispatcher can lookup provider.
dbHandle.
>3) Increase subsystem with fb_engine_info() method only.For this purpose we already have isc_service_attach() which has
>fb_engine_info() has nodePath (string) which for example holds
>servername(s) (and engine name?).
"service" param that holds servername (and engine name?).
>I think 1 will make dispatcher to complex, because it has to implementNot so complex because all things you are thinking about must be
>a service which needs to do many things (think about quering running
>progress etc..).
served not in dispatcher but in providers. Dispatcher is for global
things only.
>Option 2 looks a nice way to handle the problem.If we forget that it duplicates functionality of
isc_database_info().
>3 Is also a nice, but dispatcher requires a little bit moreExactly the same amount of functionality as case 1).
>functionality.
--
SY, Dimitry Sibiryakov.