9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Streaming 9P is out
Date: Sat,  8 Jan 2011 18:42:33 -0800	[thread overview]
Message-ID: <AANLkTi=ExqHbTkYKFc3wq=pyrWJYbsLzCcU79CPGgTxY@mail.gmail.com> (raw)
In-Reply-To: <7667f336f8ad5ad9b10d8612d6014c7b@gandalf.orthanc.ca>

On Sat, Jan 8, 2011 at 6:24 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
<lyndon@orthanc.ca> wrote:
>> thinking about it... why not just let stream() fail and let the program
>> decide if it makes sense to continue without it?
>
> Exactly what I was thinking.  If the program requires the semantics of
> stream(), it should be able to reliably discover when they aren't
> available.

I prefer John's approach. It's a trivial change and doesn't require
most programmers to think too hard. Bear in mind that if you don't
want to use John's functions, you don't have to: all those decisions
are made at library level. Streaming is available whether or not you
use his "client" functions.

But rather than talk this to death, the best bet is to try it out and
see. A good first cut is to pick a bunch of programs, mod them to use
streams, and we can see which approach makes the most sense. Learn By
Doing.

ron



  reply	other threads:[~2011-01-09  2:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  7:24 John Floren
2011-01-08 10:45 ` Seed
2011-01-08 13:11   ` Bruce Ellis
2011-01-08 15:16 ` David Leimbach
2011-01-09  0:31 ` cinap_lenrek
2011-01-09  0:46   ` John Floren
2011-01-09  1:05     ` erik quanstrom
2011-01-09  1:53     ` cinap_lenrek
2011-01-09  2:24       ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-01-09  2:42         ` ron minnich [this message]
2011-01-09  1:58     ` cinap_lenrek

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='AANLkTi=ExqHbTkYKFc3wq=pyrWJYbsLzCcU79CPGgTxY@mail.gmail.com' \
    --to=rminnich@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).