cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@dff.st>
Subject RE: validity information
Date Mon, 29 Apr 2002 09:49:29 GMT
<snip/>

> > Specifing the dependencies inside as sitemap parameter by hand sucks...
> > ..although it is a possible sollution ;)
> >
> > When the transformer could get the Validities of the previous pipeline
> > components (or at least the last one) this should be sufficient I guess.
> >
> > Carsten, or others... any idea how to obtain this information?
> > ...I am not sure if this possible at all...
> >
> Ok, I'm trying to be very wise today: ;)
>
> <turning on wise mode>
>
> It is not possible and not allowed because SoC
>
> <turning off wise mode>

*sigh* somehow I knew you would say that ;)

> Now, of course, I'm interested on why you need this information?

Well, the transformer collects and stores some information that has a
different validity than the pipeline data.

Let's assume a transformer that inserts data. So this means it's validity
depends on....

Transformer Output Validity depends on:
1)
  a) the validity of the previous pipeline components
  b) the validity of the data that get's inserted by the transformer

Now the transformer also gathers information that only comes from the
pipeline. So the validity of this information only depends on the validity
of the previous pipeline components.


Gathered Information Validity:
2)
 a) the validity of the previous pipeline components

What I am trying to achieve is not to change the gathered information when
2b) changes but only when 1a) = 2a) changes.

> I could imagine writing one pipeline components (stream and event
> pipeline) which handles this.

Could you please elaborate a bit more?

Thanks
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message