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

List:       kde-pim
Subject:    Re: [Kde-pim] icaldir Proposal
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2005-10-20 21:37:20
Message-ID: 200510202337.30306 () erwin ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 20 October 2005 06:39, Mark Bucciarelli wrote:
> On Wed, Oct 19, 2005 at 10:25:40PM +0200, Ingo Kl?cker wrote:
> > Who creates the lockduration file?
>
> Any client app can create this, unless the admin set's file
> permissions to prohibit this.

I guess I have to ask more precise questions. I want to know when this 
file is created (on creation of the icaldir?) and, more importantly, 
whether it's ever supposed to be changed.

> > Why is a configurable lock duration necessary?
>
> I have had at least three bug reports of stale locks in karm and have
> seen at least one other here on this list.  By using a lock duration,
> we can tell for sure if a lock is stale or not.
>
> But maybe your question was why configurable?

Yes, that was my question.

> A fish:// resource over dialup would have a different lockduration
> than a local file.  I wanted to be able to support both.

But the remote fish:// resource is a local resource on the remote 
machine.

Regards,
Ingo

[Attachment #5 (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]