From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Design of webfs and webcookies
Date: Mon, 25 Jan 2010 15:59:49 -0500 [thread overview]
Message-ID: <022d7d3e2065ecf32c550d52f34dd473@brasstown.quanstro.net> (raw)
In-Reply-To: <019DE3DC-AEAF-489A-8583-AC031FE3C073@fastmail.fm>
On Mon Jan 25 15:15:42 EST 2010, eekee57@fastmail.fm wrote:
>
> On 13 Jan 2010, at 4:23 pm, Enrico Weigelt wrote:
>
> > * erik quanstrom <quanstro@quanstro.net> wrote:
> >
> >> i think you misunderstand the problem. cookiefs' fs interface
> >> is not the issue. cookiefs' robustness when storing the cookies
> >> on the fileserver in the face of multiple concurrently running
> >> cookiefs' is.
> >
> > ah, you're talking about the situation when multiple cookiefs
> > instances running on the same storage ? hmm, that's the classical
> > multi-access problem ;-O
> >
> > but how do you get into that situation in the first place ?
> > (more to the point: who starts these multiple instances ?)
>
> Wouldn't multiple instances of cookiefs neatly provide transaction
> isolation?
i don't see how you could get acid semantics without locking
the cookie file for the duration of each http exchange. this is because
one can't predict the returned cookies or abort the request and try
again. sending the same http request twice might end up charging
your credit card twice.
i'm not sure this level of inconsistency matters.
- erik
next prev parent reply other threads:[~2010-01-25 20:59 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
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 [this message]
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=022d7d3e2065ecf32c550d52f34dd473@brasstown.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).