From: Michael Fellinger <m.fellinger@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Question: Rack::CommonLogger
Date: Mon, 19 Oct 2009 20:13:55 +0900 [thread overview]
Message-ID: <9c00d3e00910190413l3321fa84jb0c02db312a9ddf8@mail.gmail.com> (raw)
In-Reply-To: <69153eee-df41-458d-bb21-baf471302808@v37g2000prg.googlegroups.com>
On Mon, Oct 19, 2009 at 9:08 AM, Max <nanodeath@gmail.com> wrote:
>
> In Rack::CommonLogger, how come the logger duplicates itself on each
> call? (according to http://rack.rubyforge.org/doc/classes/Rack/CommonLogger.html)
> Is it necessary, or to clear some sort of state, or...??
>
> Just curious, was thinking of making my own logger and not sure under
> which conditions I need to duplicate.
>
> Thanks,
> Max
At least in HEAD, it doesn't duplicate anymore:
http://github.com/rack/rack/blob/master/lib/rack/commonlogger.rb
--
Michael Fellinger
CTO, The Rubyists, LLC
972-996-5199
prev parent reply other threads:[~2009-10-19 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 0:08 Question: Rack::CommonLogger Max
2009-10-19 11:13 ` Michael Fellinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c00d3e00910190413l3321fa84jb0c02db312a9ddf8@mail.gmail.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).