s the functionality i
am looking for.
TIA,
Michael
> -Original Message-
> From: Daniel Fagerstrom [mailto:[EMAIL PROTECTED]]
> Sent: vrijdag 8 maart 2002 1:36
> To: [EMAIL PROTECTED]
> Subject: RE: Pipe-aware Selectors
>
>
> Michael Homeijer wrote:
>
> > I have the
Nicola Ken Barozzi wrote:
>
> From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
>
> > Nicola Ken Barozzi wrote:
> >
> > > It seems that the dual nature of the processing in Cocoon is starting to
> get
> > > tested by sensible argumentations.
> >
> > I'm sorry, Ken, but I don't get your point about t
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
> Nicola Ken Barozzi wrote:
>
> > It seems that the dual nature of the processing in Cocoon is starting to
get
> > tested by sensible argumentations.
>
> I'm sorry, Ken, but I don't get your point about this 'dual nature', can
> you elaborate more?
Daniel Fagerstrom wrote:
> I have done some more thinking and have started to build a prototype. I
> decided that it would be easier to build it in the treeprocessor, so I will
> describe the design this far in terms of the treeprocessor interfaces and
> classes.
> Given that the design above
Nicola Ken Barozzi wrote:
> It seems that the dual nature of the processing in Cocoon is starting to get
> tested by sensible argumentations.
I'm sorry, Ken, but I don't get your point about this 'dual nature', can
you elaborate more?
--
Stefano Mazzocchi One must still have chaos in ones
On Thu, 7 Mar 2002, Stefano Mazzocchi wrote:
> giacomo wrote:
>
> > In fact I don't think we can change the Selector interface as it is
> > clearly stated what a Selector is and how it works (read: not a pipeline
> > component). It doesn't mess with the SAX event in a pipeline (also for
> > backw
Michael Homeijer wrote:
> I have the following situation:
> (1) I have a form with data (requestgenerator),
> (2) the data is validated by a validating transformer (in case of failure
> see 5b)
> (3) the data is transformed into xmldb transformer syntax (by xslt)
> (4) the data is transformed by
Stefano Mazzocchi wrote:
> Daniel Fagerstrom wrote:
>
> > The pipe-selector (ideas about a better name?) would look something like
> > this:
> >
> >
> >
> >
> >
> >
> >
> > ...
> >
> >
> >
> >
> >
> > The general idea is that the pipe-selector buffers it inpu
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
...
> I see three solutions:
>
> 1) ignore the proposal (but we must find a way to implement the same
> functionality without hacks!)
> 2) change the Selector interface
> 3) add another pipeline-aware routing sitemap component
>
> Tough decision ind
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
...
> I see three solutions:
>
> 1) ignore the proposal (but we must find a way to implement the same
> functionality without hacks!)
> 2) change the Selector interface
> 3) add another pipeline-aware routing sitemap component
>
> Tough decision ind
Vadim Gritsenko wrote:
> > > What do others think about this?
>
> The more I read about "pipeline selectors" the less I like them (DOM
> tree building, re-streaming, ...)...
I know, I know, I have the exact same impression myself :/
> However, don't you think that there is some overlap between
giacomo wrote:
> In fact I don't think we can change the Selector interface as it is
> clearly stated what a Selector is and how it works (read: not a pipeline
> component). It doesn't mess with the SAX event in a pipeline (also for
> backwards compatability).
Yes, that's a good point, but the s
> -Original Message-
> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
> Sent: woensdag 6 maart 2002 14:57
> To: [EMAIL PROTECTED]
> Subject: RE: Pipe-aware Selectors
>
>
> > From: giacomo [mailto:[EMAIL PROTECTED]]
> >
> > On W
> From: giacomo [mailto:[EMAIL PROTECTED]]
>
> On Wed, 6 Mar 2002, Stefano Mazzocchi wrote:
>
> > Michael Homeijer wrote:
> > >
> > > Hi Stefano,
> > >
> > > Could you please have another look at the solution described by
Bruno
> > > Dumon
> > > in the mailing list and comment on it.
> > > I'd r
On Wed, 6 Mar 2002, Stefano Mazzocchi wrote:
> Michael Homeijer wrote:
> >
> > Hi Stefano,
> >
> > Could you please have another look at the solution described by Bruno Dumon
> > in the mailing list and comment on it.
> > I'd really like to know what you think about it.
> >
> > It seperates the s
Michael Homeijer wrote:
>
> Hi Stefano,
>
> Could you please have another look at the solution described by Bruno Dumon
> in the mailing list and comment on it.
> I'd really like to know what you think about it.
>
> It seperates the small incoming parts of data from the outgoing flow,
> doesn't
Hi Stefano,
Could you please have another look at the solution described by Bruno Dumon
in the mailing list and comment on it.
I'd really like to know what you think about it.
It seperates the small incoming parts of data from the outgoing flow,
doesn't change any cocoon interfaces, and you will
17 matches
Mail list logo
