W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2006

Are components side-effect free?

From: Alessandro Vernet <avernet@orbeon.com>
Date: Fri, 28 Apr 2006 18:24:03 -0700
Message-ID: <4828ceec0604281824t2d4d7b23i41c80e2787192587@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

I think we are getting closer to having a consensus on issue 3096:

Issue 3096
Are components side-effect free?

On 4/26/06, Norman Walsh <Norman.Walsh@sun.com> wrote:
> I propose that we say that all components are non-functional. That is,
> a pipeline implementation must behave as if it evaluated a component
> every time it occurs [in the context of this message, everytime it is
> used in a step]. "Must behave as if" is spec-ease for "implementations
> that are clever enough to determine with certainty that a component
> is, in fact, functional are free to cache the intermediate results
> because by golly if it is, no one will be able to tell."

Our answer could be: The pipeline language does not mandate components
to be side-effect free. It is expected that amongst the components
provided by an implementation, some will be side-effect free, while
other will have side-effects. Some implementations are expected to
perform some type of caching. They will leverage the information they
have cached combined with their knowledge of components to skip the
evaluation of some steps. To be considered conformant, an caching
implementation must exhibit an behavior equivalent to a conformant
implementation that does not perform any caching.

Blog (XML, Web apps, Open Source):
Received on Saturday, 29 April 2006 01:24:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:39 UTC