[Web-SIG] serving (potentially large) files through wsgi?

Phillip J. Eby pje at telecommunity.com
Tue Jan 15 16:16:29 CET 2008

At 02:05 PM 1/15/2008 +0000, Chris Withers wrote:
>Phillip J. Eby wrote:
>>>Why would they need to? The logging module has its own registry of loggers.
>>>getLogger('x.y.z') only creates a logger if it doesn't already exist...
>>You're only shifting the issue from taking loggers as arguments, to 
>>logger *names* as arguments.
>Huh? How so? Just compute the logger name where you need it, or use 
>a page path or however you want to slice'n'dice your loggers...

And how is, say, an SQL connection object supposed to know what the 
"page path" is?  That was the whole point of this thread: that 
without passing logger objects around, or having some other dynamic 
context, there's no way for libraries to direct their log information 
to the right place.

More information about the Web-SIG mailing list