9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@googlemail.com>
To: lucio@proxima.alt.za,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How would you go about implementing this in Plan9?
Date: Fri, 10 Dec 2010 10:58:13 +0100	[thread overview]
Message-ID: <AANLkTikChH_as6-4UVAsyXJzyiyudSoWYvoofy0VRM7P@mail.gmail.com> (raw)
In-Reply-To: <20101210094607.GF4184@fangle.proxima.alt.za>

Sometimes simple traditional apps with stdin and stdout will also suffice...

On 12/10/10, Lucio De Re <lucio@proxima.alt.za> wrote:
> On Fri, Dec 10, 2010 at 11:34:41AM +0200, Eugene Gorodinsky wrote:
>> Date: Fri, 10 Dec 2010 11:34:41 +0200
>> From: Eugene Gorodinsky <e.gorodinsky@gmail.com>
>> To: 9fans@9fans.net
>> Subject: [9fans] How would you go about implementing this in Plan9?
>>
>> Suppose you're writing an app such as a multiprotocol instant messenger or
>> a
>> mediaplayer that supports multiple container formats and codecs. It's a
>> good
>
> You build them all into the synthetic files server, but only activate the
> needed ones as commanded through a control channel or file.  In such
> case, you can define the communication mechanism and may do better
> than with loadable modules, where you can never be certain that they'll
> be available.
>
> ++L
>
>



  reply	other threads:[~2010-12-10  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10  9:34 Eugene Gorodinsky
2010-12-10  9:46 ` Lucio De Re
2010-12-10  9:58   ` hiro [this message]
2010-12-10  9:46 ` hiro
2010-12-10 10:01   ` Lucio De Re
2010-12-10 10:30 ` Charles Forsyth
2010-12-10 11:21   ` Eugene Gorodinsky
2010-12-11  1:43     ` Nathaniel W Filardo
2010-12-11 19:02       ` Eugene Gorodinsky
2010-12-10 15:52   ` David Leimbach
2010-12-10 20:01     ` Eugene Gorodinsky
2010-12-10 20:33       ` Federico G. Benavento
2010-12-11 19:01         ` Eugene Gorodinsky
2010-12-10 11:47 ` Federico G. Benavento
2010-12-10 13:23 ` erik quanstrom

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=AANLkTikChH_as6-4UVAsyXJzyiyudSoWYvoofy0VRM7P@mail.gmail.com \
    --to=23hiro@googlemail.com \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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).