|Subject||Re: Engine information (nr. of attachments, databases, db-name-info) for vulcan|
> This is how i understand it:My understanding of the provider did not include the services. I will
> A provider isn't necessary a engine, it can also be remote or
> services. They all inherited from a subsystem where abstract methods
> are defined. Every provider overrides the method it can support.
re-read the provider architecture by Jim and check the code.
> I'm really missing your point here, the current services modulelIn this case I have some problems in understanding the layring of this
> seems to be what you describe.
thing... Services module(s) in my understanding must not be on the
same level with engine providers. I will come back after reading the
docs and the code.