RemoteNB 1.06 & Lockfiles

[Tom Hughes]

In message <a0b52d8549.rav21 at wallace.mk-net.demon.co.uk>
          Richard van der Hoff <rav21 at cam.ac.uk> wrote:

> I note you've been fixing your lock-handling code.  Indeed, the inbox does
> seem to get locked, which I guess is a Good Thing.  It does mean, however,
> that, when I choose to read my mail via Pine, it can't get write access to
> my inbox.  I'm not sure if that's a huge problem, but how viable would it
> be to unlock the mailbox when you're not scanning it?

I removed the change that I originally made for you which ensured
that folders were opened for read most of the time because I had
put in proper support for the UW IMAP server's lock stealing so
that RemoteNB will now reopen the connection when it closes because
another program steals the lock.

Are you saying that Pine isn't managing the steal the lock? That seems
very odd... Are you using Pine to access you mailbox via IMAP or by
direct access to the folders on local disk?

> None of the other folders seem to get locked in the same way: is that
> intentional/unintentional/Pine's fault anyway?

Typically RemoteNB will only have one folder locked at a time and
that is which ever one was accessed last. Note that RemoteNB itself
doesn't control the locking - any locking is entirely up to the
server so a server that keeps messages in a database with proper
locking and transaction control won't need to lock whole folders.

> I'm looking forward to your message-fetches-during-a-scan code...

I'm running a test version of it right now ;-)

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/
...What do you call a man with no arms or legs in the pool? Bob