Subject Re: [Firebird-Architect] Re: Vulcan services engine info. was (engine information (nr. of attachments, da
Author Arno Brinkman

> But now I have another question - why don't we move processing of the
> Services API completely to the dispatcher and extend the subsystem
> interface to execute database related service calls (like
> backup/restore, gfix things, db properties, etc.)?

> In this case all what we talk here will get its logic and beauty - all
> database specific calls are handled by the engine providers, calls
> that span multiple databases/providers - by the dispatcher. Initial
> call comes into the dispatcher which a) knows what kind of call it is;
> b) forwards the call to the needed endpoint; c) or processes the call
> itself.

Personally i don't like this, IMO the dispatcher is just a provider which map the calls to other providers. Don't give
it information wat doesn't belong there.

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: