Re: Optimising #include creation of FastWriter

On Thursday 09 March 2006 23:11, Keats Kirsch wrote:
> If my memory serves (which is dubious) the FastWriter caches an entire
> page before flushing to the output stream.  This was a controversial
> design decision -- there were a lot of complaints about potential
> performance impacts, but no metrics that I'm aware of.  At one point I
> developed a #flush directive to work around this for a particular
> application.
>
Yes, Lane and I gave up on trying to reintroduce the lost functionality in 
Melati. 
It is still missed. 

If you are trying to paginate a book this is a process that might take fifteen 
or more minutes, so the status page needs to be updated every page or chapter 
to keep the browser believing something is happening. 

Really nice to see some activity on WM.

Cheers
tim pizey

-- 
Registered linux user #21337, http://counter.li.org.


-------------------------------------------------------
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