> BufferedLogger appears to just implement write buffering, which is > normally the job of the operating system. I'm assuming I'm missing > something, but I'm having trouble finding any justification for it > anywhere. Can someone explain why we have it?
The short version is that logging showed up in hello world benchmarks and as a result some optimisation, of questionable real world utility, took place. Buffering up a bunch of writes into a single write does make a difference though and it seems mostly harmless. It also has some nice benefits now that it prevents interleaving of requests in multi-threaded mode. You can set your own logger instance in application.rb if you want to use something simpler / customised. -- Cheers Koz -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
