[Portland] Current plan summarized

[Lubos Lunak]

On Wednesday 15 March 2006 16:08, Dan Kegel wrote:
> On 3/15/06, nf2 <nf2 at scheinwelt.at> wrote:
> > I'm still not convinced regarding the static linking of the interface
> > library. We have not discussed this thoroughly and perhaps it's too
> > early to decide. I think there are two options here:
> >
> > 1) Standardize protocol, socket locations, dapi-daemon startup-scripts...
> > 2) Standardize the API of a dynamically linked dapi-client library (You
> > can still have convenience wrappers for C++,...), hiding all the IPC
> > complexity.
>
> There's a third option:
>
> 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. Also, at least in KDE's case, your 
additional costs argument shouldn't really apply (seriously, eventually).

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/