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

Re: Auxiliary documents

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 13 Apr 2006 10:59:15 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87psjlplmk.fsf@nwalsh.com>
/ Alessandro Vernet <avernet@orbeon.com> was heard to say:
| A static execution order, that can be determined just by "looking at a
| pipeline", makes the pipeline language simpler. This is good thing.
| However, it prevents an implementation from performing clever caching.
| In my experience, because of the use cases I am working with, caching
| is very important.

I don't see how the constraint that order be determined before
execution begins impacts caching. I'm not suggesting that the
components have to be bolted together so that each component is forced
to parse everything. I just don't want the engine to have to back
track to determine what component would need to be executed to create

| I think that an implementation should be allowed to implement this
| type of behavior.

Me too.

                                        Be seeing you,

Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Received on Thursday, 13 April 2006 14:59:33 UTC

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