[Portland] Current plan summarized

[Lubos Lunak]

On Thursday 16 March 2006 22:58, Jon Cruz wrote:
> On Thursday, March 16, 2006, at 09:34 AM, nf2 wrote:
> > ... standardizing IPC means you have to make all those final decisions
> > about:
> >
> > -) How to start the daemon if it's not running? Running a
> > startup-script?
> > -) When to start the daemon (at the beginning of a desktop session /
> > on demand?)

 If at the beginning of a desktop session, then starting is not the app/lib's 
problem at all. If that's a problem, a simple shell variable pointing to a 
command can solve the problem.

> > -) How many daemon processes (single/one per application)?

 Not the app/lib's problem.

> > -) Name/location of the socket? (careful! it might have to stay in the
> > same place for the next 10 years)

 It should do just fine next to the DCOP or DBUS socket. Symlinks or the DCOP 
technique of having a text file that contains the actual socket name can take 
care of possible moving later (although I don't really see why).

> > -) Which protocol to use (homegrown, dbus-1.0, dbus-2.0,...)?
> > -) Perhaps clients have to read a config-file to look up the socket
> > name. Where to find the config-file?

 They don't, it's hardcoded in the source.

>
> Perhaps Zeroconf for discovery?

 Why?

-- 
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/