[Seaside] XHTML is a tree, not a stream

[Damien Cassou]

Hi,

in my opinion, XHTML is best considered as a tree than as a stream. I 
wonder if Seaside would benefit from a tree representation. Some ideas 
come to my mind:

- it would be possible to modify a previously rendered node/tag (adding 
content or changing parameters)
- #with: would not be necessarily at the end anymore (because the tag is 
really closed when the tree is converted to the stream)
- Seaside would then have one representation of a document (a tree) that 
can be easily converted to multiple kind of output (XHTML, LaTeX, other 
XMLs...)
- there might be other advantages

One of the drawbacks would be that Seaside would not be able to send the 
stream directly to the web browser while it renders components. It would 
need to wait for the end. But if I remember correctly, it is already the 
case.

Do you have an opinion ?

-- 
Damien Cassou