From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <599f06db0609040752n7a0bbb7dh7fee10b0d08bcd0@mail.gmail.com> Date: Mon, 4 Sep 2006 08:52:48 -0600 From: "Gorka guardiola" 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 In-Reply-To: <200609031909.k83J9UV23187@demeter.cs.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609031909.k83J9UV23187@demeter.cs.utwente.nl> Topicbox-Message-UUID: b036e3b0-ead1-11e9-9d60-3106f5b1d025 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 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