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] 9ttp
Date: Thu,  8 Sep 2011 09:21:50 -0700	[thread overview]
Message-ID: <CAJJ04x4p690id2ruDv5EFAOf6pkeLBae-rZ7dmONjGX39LkpPw@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XN_NcKfMzugkhoj2CTaBF6Gfdke0XstEjPqcjr9FswpPw@mail.gmail.com>

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

On Thu, Sep 8, 2011 at 1:51 AM, hiro <23hiro@googlemail.com> wrote:

> HTTP is technically different and not easily comparable to 9p. HTTP is
> not a good example of how to do things, but over high-latency links 9p
> is much slower for getting files.
>
> HTTP tries to be stateless as well.  Hence REST.  9p is a fairly stateful
protocol.
... but then so is NFSv4, and 9p remains simpler.

There's also pi-P documented somewhere that takes the ideas of 9p and makes
them more applicable to the space where http is interesting, as well as
others.

Dave

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

  reply	other threads:[~2011-09-08 16:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08  8:36 s s
2011-09-08  8:51 ` hiro
2011-09-08 16:21   ` David Leimbach [this message]
2011-09-08  9:09 ` dexen deVries
2011-09-08  9:17   ` Steve Simon
2011-09-08  9:22   ` dexen deVries
2011-09-08 12:34     ` hiro
     [not found] ` <CAFSF3XN_NcKfMzugkhoj2CTaBF6Gfdke0XstEjPqcjr9FswpPw@mail.gmail.c>
2011-09-08 12:54   ` erik quanstrom
2011-09-08 13:04     ` dexen deVries
2011-09-08 16:24       ` David Leimbach
     [not found]       ` <CAJJ04x7xC4iuqm0HOzKN-Jb3FSmg8w1E+1Lc06pYaOm_diBNsQ@mail.gmail.c>
2011-09-08 16:31         ` erik quanstrom
2011-09-08 16:56           ` John Floren
2011-09-08 16:59             ` ron minnich
2011-09-08 17:18               ` David Leimbach
     [not found]             ` <CAP6exYJSScKcavDvR55KqJyG5-GphLQxV_+-WuwzgU3CH0pV8w@mail.gmail.c>
2011-09-08 17:20               ` erik quanstrom
2011-09-08 17:28                 ` EBo
2011-09-08 19:44             ` Bakul Shah
2011-09-08 20:14               ` John Floren
2011-09-08 20:35                 ` Bakul Shah
2011-09-08 20:43                   ` Francisco J Ballesteros
2011-09-08 22:49                     ` Bruce Ellis
2011-09-08 23:19                       ` Venkatesh Srinivas
2011-09-08 23:29                         ` ron minnich
2011-09-08 23:48                           ` Venkatesh Srinivas
2011-09-09  0:18                       ` Eric Van Hensbergen
     [not found]                   ` <CAP6exYKARAZWWWXfK6myj+y47k3XmNnyF4z17zuHOZHczxDOhw@mail.gmail.c>
2011-09-08 23:32                     ` erik quanstrom
2011-09-08 23:51                       ` Venkatesh Srinivas
2011-09-09  8:13                         ` Charles Forsyth
2011-09-09  9:26                           ` Bruce Ellis
2011-09-09  9:36                             ` dexen deVries
2011-09-09 11:26                               ` Bruce Ellis
2011-09-08 20:18               ` erik quanstrom

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=CAJJ04x4p690id2ruDv5EFAOf6pkeLBae-rZ7dmONjGX39LkpPw@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).