[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Question on Akonadi data connection
From:       Tobias Koenig <tokoe () kde ! org>
Date:       2007-07-30 19:23:23
Message-ID: 20070730192323.GA8496 () ghostdog ! localnet
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Mon, Jul 30, 2007 at 09:01:23PM +0200, Kevin Krammer wrote:
> Hi Tobias,
Hi Kevin,

> > > 2) The socket address should rather be an abtract unix socket, e.g. like
> > > D-Bus Currently, if the akonadiserver crashed, it leaves the socket
> > > around and cannot listen on it anymore
> >
> > We just have to unlink the unix socket file on a restart of akonadi.
> > That's a know issue with unix domain sockets.
> 
> The current hardcoded socket path is a problem (besides being hardcoded) if 
> the file system hosting $HOME is not capable of having sockets.
> 
> In a KDE application we would use KStandardDirs to locate a suitable socket 
> directory, abstract Unix sockets avoid this problem alltogether.
Ahh, you mean KLocalSocket::AbstractUnixSocket with abstract unix
sockets :) Well, using them makes sense indeed :)

> I am not sure how far the D-Bus Windows people have come sofar since they have 
> the same issue.
> I though that maybe using the same address format as D-Bus might give us 
> better flexibility in the long term. 
Yepp

Ciao,
Tobias
-- 
Separate politics from religion and economy!
The Council of the European Union is an undemocratic and illegal institution!

["signature.asc" (application/pgp-signature)]

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]