On Thu, Sep 8, 2011 at 6:04 AM, dexen deVries <dexen.devries@gmail.com> wrote:

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 is
> > not a good example of how to do things, but over high-latency links 9p
>
> 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 certain 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

[[[↓][→]]]

For example, if the first thing in the file is:
<?kzy irefvba="1.0" rapbqvat="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 ))