Subject | Re: [Firebird-Architect] Vulcan services part II |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-05-11T11:30:57Z |
On 11 May 2006 at 12:16, Arno Brinkman wrote:
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.
All that is needed - make it to use engine classes instead of Y-valve
and link it into engine.
--
SY, Dimitry Sibiryakov.
>But services provider is currently not ODS dependend and configurableRight. But there are services and services. It is exactly like
>and directly using engine11 would ignore that part. Adding/Modifing a
>user does that belong to the engine? Not when we're talking a global
>user-repository. These are things for the service, right?
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.
>I agree with you that engine could support tasks for backup/restore,No, it is exactly the same backup. And it is already implemented.
>but that would be an other backup/restore than gbak currently does.
>Currently it's really not the time to implement this.
All that is needed - make it to use engine classes instead of Y-valve
and link it into engine.
--
SY, Dimitry Sibiryakov.