cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolás Lichtmaier <>
Subject Re: Content-length
Date Mon, 24 Jan 2000 03:09:39 GMT
> dunno if that's possible. if there is a concept of blocking
> and nonblocking nodes, then any methods on a node for
> getting children or values or attributes may need to throw
> some kind of acception until the node is unblocked. which
> means an api change. furthermore you need to be able to
> specify that a node blocks when you construct it.

 If the node blocks for a while and then continues everything is OK, the
contract is not broken. It's the normal consumer-producer relationship.
 So the consumer accesses the DOM, without caring that the underlying data
is still arriving via SAX events. When the node is blocking, this engine is
waiting for the SAX events that conform the node to arrive...

 Note that this component would be completely generic: A DOM view over a SAX
stream. So it is not a Cocoon infrastructure decision: each component cand
do as it likes...

 An issue: Would be ok to modify the partial tree?

View raw message