Re: Optimising #include creation of FastWriter

| 
| Just out of interest - how were you envisioning this rolling back happening?  
| Was it going to be a java space action or would it take place during the 
| template rendering phase?

I already do this, dude - so all your arguments about why it ain't smart 
is simply not applicable.

The clue is that this is a _portlet engine_, right? Every portlet operates 
on its own, and you may view the portal as an operating system with the 
portlets as applications. If you understand this view, then I guess you 
understand why containment of errors are both smart and correct, and the 
"internal state change" arguments are simply not interesting (Better to 
contain _one_ error than make it propagate all the way out to the users 
browser, so that he potentially can't see the portal page at all (due to 
messed up nesting of tables etc)).

I do it using _a new_ FastWriter with a temporary backing, then if 
everything went right, I put the result to the FastWriter.

This temporary backing paradigm obviously isn't the best, and a 
mark/reset/flush paradigm would be much better for my part.

Regards,
Endre.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642