Graham Dumpleton ha scritto:
> [...]
>> Too complex, IMHO.
>
> Actually, if you don't try and bind it back to a specific request, and
> just use the main error log file, it is actually quite easy.
>
>> I think that it is better to have two separate logging objects.
>> wsgi.errors and sys.stderr,
On 24/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
> > As for everything else, as suggested in a previous email, you would be
> > better off basing anything else beyond sys.stderr and wsgi.errors off
> > the Python 'logging' module. In doing this, nothing would be required
> > in the WSGI env
Graham Dumpleton ha scritto:
> On 24/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
>> Graham Dumpleton ha scritto:
>>> Whatever you do, please do not go releasing any distinct Python
>>> module/package called 'mod_wsgi' as the Apache mod_wsgi code is all
>>> set up around it being able to do t
Ian Bicking ha scritto:
> Manlio Perillo wrote:
>> By the way: any proposal for "standardize" common "namespaces"?
>
> Yes, see: http://wsgi.org/wsgi/Specifications
>
> Note that it also requires some enthusiasm from more than one person to
> actually move through this otherwise fairly casual pr
On 24/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
> Graham Dumpleton ha scritto:
> > Whatever you do, please do not go releasing any distinct Python
> > module/package called 'mod_wsgi' as the Apache mod_wsgi code is all
> > set up around it being able to do that already, with the assumption
Graham Dumpleton ha scritto:
> On 23/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
>> Hi.
>>
>> As I have written in a previous thread, I would like to use nginx
>> logging system in a WSGI application (of course the same is valid for
>> Apache)
>>
>> A first problem is that the wsgi.errors st
Graham Dumpleton ha scritto:
> [...]
>
> Please don't use 'mod_wsgi', use 'nginx' as you originally said.
>
> There is already going to be enough confusion around you using the
> 'mod_wsgi' name when the Apache WSGI implementation came first. I
> really wish now that I had insisted you specifical
On 23/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
> Hi.
>
> As I have written in a previous thread, I would like to use nginx
> logging system in a WSGI application (of course the same is valid for
> Apache)
>
> A first problem is that the wsgi.errors stream defined in the
> environment dict
Manlio Perillo wrote:
> By the way: any proposal for "standardize" common "namespaces"?
Yes, see: http://wsgi.org/wsgi/Specifications
Note that it also requires some enthusiasm from more than one person to
actually move through this otherwise fairly casual process; several
attempts to standardi
On 23/11/2007, Manlio Perillo <[EMAIL PROTECTED]> wrote:
> Phillip J. Eby ha scritto:
> > At 11:57 AM 11/23/2007 +0100, Manlio Perillo wrote:
> >> Hi.
> >>
> >> As I have written in a previous thread, I would like to use nginx
> >> logging system in a WSGI application (of course the same is valid f
At 01:25 PM 11/23/2007 +0100, Manlio Perillo wrote:
>Phillip J. Eby ha scritto:
>>At 11:57 AM 11/23/2007 +0100, Manlio Perillo wrote:
>>>Hi.
>>>
>>>As I have written in a previous thread, I would like to use nginx
>>>logging system in a WSGI application (of course the same is valid for
>>>Apache)
>
Phillip J. Eby ha scritto:
> At 11:57 AM 11/23/2007 +0100, Manlio Perillo wrote:
>> Hi.
>>
>> As I have written in a previous thread, I would like to use nginx
>> logging system in a WSGI application (of course the same is valid for
>> Apache)
>>
>> A first problem is that the wsgi.errors stream de
At 11:57 AM 11/23/2007 +0100, Manlio Perillo wrote:
>Hi.
>
>As I have written in a previous thread, I would like to use nginx
>logging system in a WSGI application (of course the same is valid for
>Apache)
>
>A first problem is that the wsgi.errors stream defined in the
>environment dictionary is v
Hi.
As I have written in a previous thread, I would like to use nginx
logging system in a WSGI application (of course the same is valid for
Apache)
A first problem is that the wsgi.errors stream defined in the
environment dictionary is valid only for the current request, but I want
to use a s
14 matches
Mail list logo
