9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: yaroslav <yarikos@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9P/Styx: streaming / contigious reading
Date: Mon, 31 Aug 2009 17:20:58 +0300	[thread overview]
Message-ID: <90e9f70b35a4d82d4287fee617a89392@isd.dp.ua> (raw)
In-Reply-To: <58c8e88cdc5afad38233c3ab4bb74344@quanstro.net>

> > > did anyone already investigate how an streaming (w/o expicit read
> > > requests) could be done via 9P ?
> >
> > Why don't you use a protocol more suitable for high latencies?
>
> i think the problem rather is the tradition of having one
> outstanding message per fid.  as far as i can tell, 9p doesn't
> have this restriction.  we just use it that way.

Maybe the way fcp(1) works is the answer?

-- Yaroslav




  reply	other threads:[~2009-08-31 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 10:20 Enrico Weigelt
2009-08-31 12:59 ` hiro
2009-08-31 13:01   ` erik quanstrom
2009-08-31 14:20     ` yaroslav [this message]
2009-08-31 14:27       ` Eric Van Hensbergen

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=90e9f70b35a4d82d4287fee617a89392@isd.dp.ua \
    --to=yarikos@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).