Re: Mason 1.3 autoflush behaviour change

On Fri, Oct 15, 2004 at 09:14:53AM -0700, Jonathan Swartz wrote:
> You make a convincing case...I guess this is the way to go. But I'm 
> temped to put a warning in the logs if enable_autoflush is left 
> unspecified. :)

It sort of feels like those of us who write our own handlers should be
left to hurt ourselves as badly as we'd like, while having a sane set of
defaults for the non-handler case.  Hm. I'd almost like to see a
$m->why_is_my_mason_slow that lists off my possibly suspect configuration 
choices.

	Jesse






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