W3C home > Mailing lists > Public > xproc-dev@w3.org > November 2012

Re: Permanently sinking output ports

From: QuiXProc XProc <quixproc@gmail.com>
Date: Sat, 17 Nov 2012 12:51:49 +0100
Message-ID: <CAMUtxrN1PCfbiEw6S+c5uYwSJ+rWcfXkOAWAJ8XieqJX-H7uWw@mail.gmail.com>
To: Romain Deltour <rdeltour@gmail.com>
Cc: XProc Dev <xproc-dev@w3.org>
Hi Romain,

At QuiXProc, we tried to find some way to implement such features

The problem with your proposal is that the XProc standards doesn't say that
you read the pipeline sequentially (because of the dependency graph)

I think the only way to implement such feature nicely is that
implementation detect that they have finished to read the stream and drop it

You may have a look at QuiXProc Open 1.1.0 (
http://code.google.com/p/quixproc/ ) and tells us if it deals better with
resources

Regards,

The QuiXProc Team


On Fri, Nov 16, 2012 at 1:46 AM, Romain Deltour <rdeltour@gmail.com> wrote:

> Wouldn't it be useful to be able to specify statically at authoring time
> when a port will no longer be used after a certain point in a pipeline ?
> I'm thinking of an attribute in the p:sink element that would say "when you
> reach this p:sink, these ports will no longer be read".
>
> It would help implementors to free the memory during at execution time,
> without needing some advanced static optimization.
>
> Just a thought…
>
> Romain.
>
>
>
Received on Saturday, 17 November 2012 11:52:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 17 November 2012 11:52:17 GMT