From: "Gorka guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] trying to understand how fork/pipe a filtering program
Date: Mon, 4 Sep 2006 08:52:48 -0600 [thread overview]
Message-ID: <599f06db0609040752n7a0bbb7dh7fee10b0d08bcd0@mail.gmail.com> (raw)
In-Reply-To: <200609031909.k83J9UV23187@demeter.cs.utwente.nl>
There is a third solution. You are using it, page is using it. It is for images
(so a lot of data will probably be moving around). Convert it to a library.
If it is not a lot of data and closeness to the app is not inmportant then
your approach is probably correct (that or convertint it into a service).
On 9/3/06, Axel Belinfante <Axel.Belinfante@cs.utwente.nl> wrote:
> I continue with my own thing. I could have included the code of
> the existing program directly in mine (as page does - I actually
> first lifted that code from page), but then I'd have to track
> possible changes to that code (I don't suppose there will be many
> but that's not the point).
>
> Axel.
>
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2006-09-04 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:46 Axel Belinfante
2006-08-30 23:05 ` geoff
2006-08-31 16:26 ` "Nils O. Selåsdal"
2006-08-31 19:55 ` Axel Belinfante
2006-08-31 20:15 ` rog
2006-08-31 20:24 ` Axel Belinfante
2006-08-31 20:24 ` rog
2006-08-31 20:45 ` Axel Belinfante
2006-09-01 3:43 ` geoff
2006-09-01 10:57 ` rog
2006-09-01 14:35 ` rog
2006-09-01 15:33 ` Skip Tavakkolian
2006-09-01 15:59 ` rog
2006-09-01 18:42 ` Skip Tavakkolian
2006-09-03 19:09 ` Axel Belinfante
2006-09-04 14:52 ` Gorka guardiola [this message]
2006-09-04 20:50 ` Gorka guardiola
2006-09-04 19:26 ` Skip Tavakkolian
2006-09-04 20:25 ` Francisco J Ballesteros
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=599f06db0609040752n7a0bbb7dh7fee10b0d08bcd0@mail.gmail.com \
--to=paurea@gmail.com \
--cc=9fans@cse.psu.edu \
/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).