Mason 1.3 autoflush behaviour change

Tonight, I decided to give RT a go with the newly optimized mason. The
only problem is that we use autoflush pretty heavily, since a number of
RT's pages can take quite a while to render.  It _looks_ to me like it's
going to be impossible to support both Mason 1.2x and Mason 1.3x, if, as
I recall, mason 1.2x will scream bloody murder about the unknown
"enable_autoflush" parameter and mason 1.3 is upset that I didn't
predeclare my autoflushness.  Would it be possible to get mason 1.3x to
auto-upgrade to autoflushness the first time it sees an autoflush
directive?

	Jesse


----


As of Mason 1.3, autoflush will only work if
L<enable_autoflush|HTML::Mason::Params/enable_autoflush> has been set.
This is because components can be compiled more efficiently if they
don't have to check for autoflush. Before enabling autoflush you might
consider whether a few manual C<$m-E<gt>flush_buffer> calls would work
nearly as well.


-- 


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl