9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Design of webfs and webcookies
Date: Tue,  5 Jan 2010 10:23:34 -0500	[thread overview]
Message-ID: <5bcb0e528c3837e94d152a7a4410db21@ladd.quanstro.net> (raw)
In-Reply-To: <20100105150340.GF21460@nibiru.local>

> Just curious: can an 9P server cleanly differenciate between clients ?
> This would be a great help for transaction isolation, IMHO.
>
> w/o having looked at cookiefs yet, but I would do it like that:
>
>     * get cookies by reading /site-cookies/<site>
>     * set cookies by writing "<site>: foo=bar" to /set pipe
>       (which can stay open for as long as you want)
>
> This should minimize the amount of messages/roundtrips required in
> normal operation and make the client-side really trivial. An non-
> blocking write to the "set" file should also reduce latency
> (especially when having remote profiles)

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.

- erik



  reply	other threads:[~2010-01-05 15:23 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 [this message]
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=5bcb0e528c3837e94d152a7a4410db21@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=weigelt@metux.de \
    /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).