9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p2010
Date: Thu, 23 Apr 2009 10:38:41 -0700	[thread overview]
Message-ID: <3e1162e60904231038t340f96bfnfaa681a7f10e2b02@mail.gmail.com> (raw)
In-Reply-To: <74397773b7238fd47d00b9a51fdbfd61@quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Thu, Apr 23, 2009 at 10:28 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> > as a starting point, i'd envisaged simply changing the existing
> > system calls to do sequences.
> >
> [...]
> >
> > Sequence: adt {
> >       queue: fn(seq: self ref Sequence, m: Tmsg, tag: any);
> >       wait: fn(seq: self ref Sequence): (any, Tmsg, Rmsg);
> >       cont: fn(seq: self ref Sequence);
> >       flush: fn(seq: self ref Sequence);
> > }
>
> this is significantly more complicated than syscalls.
>
> - erik
>

Are we doing all of this to defeat the conveniences we get from the
statefulness of 9p?  Would a stateless 9p-like protocol be better (no
walks)?  Is a stateless 9p really HTTP?  :-)

If those are all yeses, are we re-inventing the wheel?  Or does 9p or some
derivative really have to get used everywhere? :-)

I mean if we figure this out, great, but if not, I think we're still ok,
just can't use 9p right?  :-)

[-- Attachment #2: Type: text/html, Size: 1440 bytes --]

  reply	other threads:[~2009-04-23 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 16:26 erik quanstrom
2009-04-23 17:22 ` roger peppe
2009-04-23 17:28   ` erik quanstrom
2009-04-23 17:38     ` David Leimbach [this message]
2009-04-23 17:31   ` Fco. J. Ballesteros
2009-04-23 17:53     ` roger peppe
2009-04-26 21:29       ` Roman V. Shaposhnik
2009-04-27  7:32         ` roger peppe
2009-04-23 17:55   ` Eric Van Hensbergen
2009-04-23 18:35     ` Steve Simon
2009-04-23 17:54 ` Gary Wright

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=3e1162e60904231038t340f96bfnfaa681a7f10e2b02@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --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).