From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Design of webfs and webcookies
Date: Tue, 22 Dec 2009 09:55:02 -0500 [thread overview]
Message-ID: <635018e058076d45e5d6bcf01860138a@ladd.quanstro.net> (raw)
In-Reply-To: <<bcba51a0912220638vb1867f3me65e9e799f9b6d87@mail.gmail.com>>
> Will anything get worse if each cookie is stored in its own file* ?
if a site has more than 1 cookie managed as a pair, you could
get them out-of-sync by not locking.
what's really wanted here is an atomic create/write/close so that
one process (we don't care which one) is responsible for the whole
file. i think you could get this behavior by creating a temporary
keyfile and then an rename (wstat), which is atomic.
- erik
next parent reply other threads:[~2009-12-22 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<bcba51a0912220638vb1867f3me65e9e799f9b6d87@mail.gmail.com>
2009-12-22 14:55 ` erik quanstrom [this message]
2009-12-22 17:56 ` Russ Cox
2010-01-05 15:03 ` Enrico Weigelt
2010-01-05 15:23 ` erik quanstrom
2010-01-13 16:23 ` Enrico Weigelt
2010-01-14 18:25 ` Russ Cox
2010-01-25 20:14 ` Ethan Grammatikidis
2010-01-25 20:59 ` erik quanstrom
2009-12-22 14:38 Dimitry Golubovsky
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=635018e058076d45e5d6bcf01860138a@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).