[Portland] Current plan summarized

[Dan Kegel]

On 3/15/06, Lubos Lunak <l.lunak at suse.cz> wrote:
> > > 1) Standardize protocol, socket locations, dapi-daemon startup-scripts...
> > > 2) Standardize the API of a dynamically linked dapi-client library ...
> > 3) Standardize on a transport that already has a daemon,
> > e.g. DBus.  Then we don't need to create a new daemon.
> > Each additional daemon at startup time costs the user
> > time and RAM.  We want at all costs to avoid bloating the
> > OS by slowing down boot or stealing RAM, I think.
>
>  Your 3) is the same like 2).  The daemon is not there to provide communication but to provide the functionality.

At this point we're just talking past each other without communicating,
I'm afraid.  If I don't have time to implement my own prototype,
I guess I should just shut up.
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv