From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Date: Thu,  8 Sep 2011 04:36:00 -0400
Message-ID: <CANPzgjQtY-sAu9ufeB6=S7iV0_WzOvKHjEZ4Q2W0bcAXpdjY9w@mail.gmail.com>
From: s s <leonardnemoi@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=20cf300fb24550eb3e04ac69f376
Subject: [9fans] 9ttp
Topicbox-Message-UUID: 1b871f18-ead7-11e9-9d60-3106f5b1d025

--20cf300fb24550eb3e04ac69f376
Content-Type: text/plain; charset=ISO-8859-1

With 9p's ability to send and receive arbitrary information as file i/o,
does http remain "necessary"?

Is there any reason that 9p cannot do this ...

''HTTP functions as a
request-response<http://en.wikipedia.org/wiki/Request-response>protocol
in the
client-server <http://en.wikipedia.org/wiki/Client-server> computing model.
In HTTP, a web browser <http://en.wikipedia.org/wiki/Web_browser>, for
example, acts as a *client*, while an application running on a computer
hosting <http://en.wikipedia.org/wiki/Host_%28network%29> a web
site<http://en.wikipedia.org/wiki/Web_site>functions as a
*server*. The client submits an HTTP *request* message to the server. The
server, which stores content, or provides *resources*, such as
HTML<http://en.wikipedia.org/wiki/HTML>files, or performs other
functions on behalf of the client, returns a
response message to the client. A response contains completion status
information about the request and may contain any content requested by the
client in its message body.''
  -- http://en.wikipedia.org/wiki/Http#Technical_overview

 - Leonard

--20cf300fb24550eb3e04ac69f376
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

With 9p&#39;s ability to send and receive arbitrary information as file i/o=
, does http remain &quot;necessary&quot;?<br><br>Is there any reason that 9=
p cannot do this ...<br><br>&#39;&#39;HTTP functions as a <a href=3D"http:/=
/en.wikipedia.org/wiki/Request-response" title=3D"Request-response">request=
-response</a> protocol in the <a href=3D"http://en.wikipedia.org/wiki/Clien=
t-server" title=3D"Client-server" class=3D"mw-redirect">client-server</a> c=
omputing model. In HTTP, a <a href=3D"http://en.wikipedia.org/wiki/Web_brow=
ser" title=3D"Web browser">web browser</a>, for example, acts as a <i>clien=
t</i>, while an application running on a computer <a href=3D"http://en.wiki=
pedia.org/wiki/Host_%28network%29" title=3D"Host (network)">hosting</a> a <=
a href=3D"http://en.wikipedia.org/wiki/Web_site" title=3D"Web site" class=
=3D"mw-redirect">web site</a> functions as a <i>server</i>. The client subm=
its an HTTP <i>request</i> message to the server. The server, which stores =
content, or provides <i>resources</i>, such as <a href=3D"http://en.wikiped=
ia.org/wiki/HTML" title=3D"HTML">HTML</a>
 files, or performs other functions on behalf of the client, returns a=20
response message to the client. A response contains completion status=20
information about the request and may contain any content requested by=20
the client in its message body.&#39;&#39;<br>=A0 -- <a href=3D"http://en.wi=
kipedia.org/wiki/Http#Technical_overview">http://en.wikipedia.org/wiki/Http=
#Technical_overview</a><br><br>=A0- Leonard<br><br><br>

--20cf300fb24550eb3e04ac69f376--