From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sent source
Date: Fri, 08 May 2009 22:10:55 -0400 [thread overview]
Message-ID: <1241834800-sup-1443@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1241702060-sup-3211@entry>
Excerpts from William Morgan's message of Thu May 07 09:23:33 -0400 2009:
> Currently sup-sync-back just says, "hey, you can use this program
> /usr/bin/dotlockfile if you have it" and pushes the details of locking
> to that. I think that's at least a vaguely reasonable approach. Ideally
> it would be more configurable, would fall back to other locking
> programs, etc., but I think it's significantly better than not doing any
> locking at all.
...Ok, what about implementing the dotlockfile functionality inside a
LockManager singleton? I'm thinking about something that would accept
a list of required locks before allowing read and write. It would
then provide with_readlock(file, &block) and with_writelock(file,
&block) methods that obtain required locks and yield to the caller to
do the actual work.
> (Eventually these two mbox writers should share the same locking code,
> but don't feel obligated to refactor as part of your patch if it's
> already getting too hairy.)
sup-sync-back could make use of this LockManager too.
Thoughts?
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090508/8b72cea9/attachment.bin>
next prev parent reply other threads:[~2009-05-09 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 0:02 Ben Walton
2009-05-07 13:23 ` William Morgan
2009-05-07 21:57 ` Ben Walton
2009-05-09 2:10 ` Ben Walton [this message]
2009-05-09 13:01 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1241834800-sup-1443@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox