Vadim Gritsenko wrote:
> > Yes, I agree. The big thing with a "precompiled site" is the
> manipulations
> > we need to do to the sitemap. I.e., we would have many many
> generators, and
> > we would have to select the proper one based on the URI. It can get
> messy,
> > but if we do it right, it won't be.
>
> Berin, it seems you are mistaken binary XMLs with compiled XSPs. There
> will be one generator for binary XMLs, not many.
And I think you both didn't get what I was proposing: ok, consider this
pseudocode:
1) I want to open an XML file, what do I do? oh, yeah, ask for a
component with the role 'parser'
2) ask the parser to parse my document
3) the parser will trigger SAX events for me on the content handler I
pass to it.
Now, suppose your XML file looks like
<?xml version="1.0"?>
<blah>
....
</blah>
all is normal.
But suppose I have this file compiled into something like this
CXMLSDSE4blahST3....ED
Now, suppose that I changed the implementation of the parser so that is
capable of understanding that if it's a *normal* XML file, it should
behave as the specification says, but if it starts with CXML (which
stands for "compiled XML", yeah my invention) it should use a parsing
behavior that is implemented in the 'XML decompiler' (which is already
implemented and used by the internal cocoon cache system).
So, you don't have to touch *anything* in your sitemap, nor in your
code, nor in your logic, nothing.
just change the role to the new *extended* parser.
Don't you just love Avalon? :)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
