From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Thu,  8 Sep 2011 11:22:07 +0200
User-Agent: KMail/1.13.6 (Linux/3.1.0-rc5-l38+; KDE/4.5.5; x86_64; ; )
References: <CANPzgjQtY-sAu9ufeB6=S7iV0_WzOvKHjEZ4Q2W0bcAXpdjY9w@mail.gmail.com>
	<201109081109.42824.dexen.devries@gmail.com>
In-Reply-To: <201109081109.42824.dexen.devries@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201109081122.07497.dexen.devries@gmail.com>
Subject: Re: [9fans] 9ttp
Topicbox-Message-UUID: 1ba407fe-ead7-11e9-9d60-3106f5b1d025

On Thursday 08 of September 2011 11:09:41 dexen wrote:
> you could create a 9p->http->9p bridge to work around high-latency links;
> it would gather a bunch of 9p operations (...)

the idea is NOT to serialize and send 9p packets themselves, but rather tha=
n=20
to translate a bunch of 9p operations into one HTTP request/response.
send one HTTP GET with proper pathname, and obtain one HTTP 200 OK with the=
=20
right content (possibly using Range header, possibly also requesting more d=
ata=20
than strictly necessary and cache it locally to serve subsequent TReads, to=
=20
avoid many HTTP requests for small amounts of data).

> could get a bit hairy for writes.

IIRC there's that `PATCH' HTTP method; not widely supported but could do.

TAuth could probably translate to HTTP Auth, at least to some extent. HTTP=
=20
itself is stateless, but a pipelined HTTP connection could be equated to on=
e=20
authenticated 9p session.

=2D-=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]

=46or example, if the first thing in the file is:
   <?kzy irefvba=3D"1.0" rapbqvat=3D"ebg13"?>
an XML parser will recognize that the document is stored in the traditional=
=20
ROT13 encoding.

(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))