On 11.Jul.2001 -- 05:06 PM, Anders Lindh wrote:
> >One of the issues is technical in nature. Because of the SAX stream
> approach
> >that Cocoon 2 uses, the XSP page is being serialized AS it is being parsed.
> >What is happening is that each SAX event (startDocument, startElement,
> etc),
> >is being propogated through the entire SAX chain and being transformed as
> they
> >are called. Once the root element has been propogated, there is no turning
> >back.
>
> Ok.. Could you clarify a bit how and in what order things are done in
> Cocoon. What
> exactly does Cocoon do with a xsp page (that has been compiled into a java
> class)? The
> compiled java class constructs a SAX document, which in turn is XSLT
> processed if needed. Right?
> Isn't this the basic flow of things?
Only that there's no SAX "document". While the XSP still generates SAX
events (document nodes), others are transformed and some are already
serialized and send to the client. Everything happens
concurrently. Thus when 50% (1%, 99%) of the document have already
reached the client what semantics should a redirect have?
C2 had a "send-redirect" in the response taglib. And if you were
lucky, the redirect was issued while the servlet engine's send buffer
was only filling up and nothing has been delivered, yet. Most of the
time the redirect never reached the client or two documents were
concatenated (i.e. IE)
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
