From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <201109081504.36357.dexen.devries@gmail.com> References: <9b73a2f7842fdf54ca57423261c7ae78@brasstown.quanstro.net> <201109081504.36357.dexen.devries@gmail.com> Date: Thu, 8 Sep 2011 09:24:31 -0700 Message-ID: From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd5288ce1a7b504ac707e28 Subject: Re: [9fans] 9ttp Topicbox-Message-UUID: 1be56b04-ead7-11e9-9d60-3106f5b1d025 --000e0cd5288ce1a7b504ac707e28 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Sep 8, 2011 at 6:04 AM, dexen deVries wrot= e: > On Thursday 08 of September 2011 14:54:40 erik quanstrom wrote: > > On Thu Sep 8 04:52:08 EDT 2011, 23hiro@googlemail.com wrote: > > > HTTP is technically different and not easily comparable to 9p. HTTP i= s > > > not a good example of how to do things, but over high-latency links 9= p > > > > with a single outstanding request > > > > > is much slower for getting files. > > > > there, fixed that for ya. > > is 9p windowable at all? is that implemented? > > > 9p has tagged requests. The client chooses them, and therefore, for certai= n servers you can overlap requests and get reasonable performance. I've designed very simplistic protocols like this before, and they typically pan out nicely. I had a simple request/response system for issuing commands to a C program that would fetch data of CAN bus connected microcontrollers. It was very nice to work with as you could drive the C program from basically any programming language. I ended up using Erlang. Go wasn't really quite available yet :-). Dave > -- > dexen deVries > > [[[=E2=86=93][=E2=86=92]]] > > For example, if the first thing in the file is: > > an XML parser will recognize that the document is stored in the tradition= al > ROT13 encoding. > > (( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt )) > > --000e0cd5288ce1a7b504ac707e28 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Thu, Sep 8, 2011 at 6:04 AM, dexen de= Vries <dexe= n.devries@gmail.com> wrote:
On Thursday 08 of September 2011 14:54:40= erik quanstrom wrote:
> On Thu Sep =C2=A08 04:52:08 EDT 2011, 23hiro@googlemail.com wrote:
> > HTTP is technically different and not easily comparable to 9p. HT= TP is
> > not a good example of how to do things, but over high-latency lin= ks 9p
>
> =C2=A0 =C2=A0 =C2=A0 with a single outstanding request
>
> > is much slower for getting files.
>
> there, fixed that for ya.

is 9p windowable at all? is that implemented?



9p has tagged requests. = =C2=A0The client chooses them, and therefore, for certain servers you can o= verlap requests and get reasonable performance. =C2=A0I've designed ver= y simplistic protocols like this before, and they typically pan out nicely.= =C2=A0I had a simple request/response system for issuing commands to a C p= rogram that would fetch data of CAN bus connected microcontrollers. =C2=A0 = It was very nice to work with as you could drive the C program from basical= ly any programming language. =C2=A0I ended up using Erlang. =C2=A0Go wasn&#= 39;t really quite available yet :-).

Dave
=C2=A0
--
dexen deVries

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

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

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


--000e0cd5288ce1a7b504ac707e28--