Subject Re: [Firebird-Architect] Vulcan services part II
Author Dimitry Sibiryakov
On 10 May 2006 at 23:35, Arno Brinkman wrote:

>1) Increase subsytem with more calls, so engine can support
>backup/restore/validate/etc...
> Dispatcher should handle the service params and implement services.

Note: not all services but only those that cannot be served by
providers.

>2) Increase subsystem with fb_engine_info() method only.
>fb_engine_info() has dbHandle so dispatcher can lookup provider.

For this purpose we already have isc_database_info() which has
dbHandle.

>3) Increase subsystem with fb_engine_info() method only.
>fb_engine_info() has nodePath (string) which for example holds
>servername(s) (and engine name?).

For this purpose we already have isc_service_attach() which has
"service" param that holds servername (and engine name?).

>I think 1 will make dispatcher to complex, because it has to implement
>a service which needs to do many things (think about quering running
>progress etc..).

Not so complex because all things you are thinking about must be
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 more
>functionality.

Exactly the same amount of functionality as case 1).

--
SY, Dimitry Sibiryakov.