From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P/Styx: streaming / contigious reading
Date: Mon, 31 Aug 2009 09:27:11 -0500 [thread overview]
Message-ID: <a4e6962a0908310727p44befa0eub464d9bd8e01134e@mail.gmail.com> (raw)
In-Reply-To: <90e9f70b35a4d82d4287fee617a89392@isd.dp.ua>
Was waiting for someone else to say it, but you should look at what
Octopus does with its operation continuation flags.
Another interesting twist on this is "lossy" streams -- but such a
thing may be best represented outside of 9P (or perhaps with a 9P
gateway).
-eric
On Mon, Aug 31, 2009 at 9:20 AM, yaroslav<yarikos@gmail.com> wrote:
>> > > 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
>
>
>
prev parent reply other threads:[~2009-08-31 14:27 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
2009-08-31 14:27 ` Eric Van Hensbergen [this message]
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=a4e6962a0908310727p44befa0eub464d9bd8e01134e@mail.gmail.com \
--to=ericvh@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).