Re: [Fwd: Re: Deva interface]

[markus kaarn]

Marcus Brinkmann wrote:
>
>  Does anybody else see other problems with making Deva a library?
>

If you define Deva as a library, what do you profit ?
Deva, as server, can serve at least as place for registering
device drivers. If client needs to access a device, he goes
for Deva and asks, if there is one he needs.

There is still, must be a place to keep device-list register.
If Deva will not serve as one. Another place will be created.
Do we really must dual the work?

If every time, i start my program and Deva-library with it. LibDeva will
have to lookup though the system-services(whatever) to find device-drivers
or plugin-managers to be used by my program. This will result in more
code execution.
On other hand, there will still be work involved between deva and ddf,
and proper interfaces between them (as i know) have to be worked out.

We must see both cases in action, so can compare? %')


Thanks,

Markus