Subject Re: [Firebird-Architect] Vulcan services part II
Author Arno Brinkman

> Right. But there are services and services. It is exactly like
> there are providers and providers.
> Backup, restore, validation, statistics, maintenance are services
> that ideally fit into engine.
> Server-wide users, config, log management are services for servier-
> wide services provider.
> Number of connections fits into Y-valve.

Currently 1 service (service_mgr) implement all these stuff and you can't separate that on two different providers.
We could use other service names, but that's not for now. First we need backwards compatibility.

>>I agree with you that engine could support tasks for backup/restore,
>>but that would be an other backup/restore than gbak currently does.
>>Currently it's really not the time to implement this.
> No, it is exactly the same backup. And it is already implemented.
> All that is needed - make it to use engine classes instead of Y-valve
> and link it into engine.

I'm not sure the engineX (ODS X) backup should be able to backup engineX-1 (ODS X-1) databases.

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: