tcl-websh-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dav...@dedasys.com (David N. Welton)
Subject Re: Logging in web::finalizer
Date Thu, 26 Feb 2004 10:51:49 GMT
Ronnie Brunner <ronnie@netcetera.ch> writes:

> 4. remove the [web::logdest delete] and [web::logfilter delete] from
> web::ap::perReqCleanup and change the implementation of web::logdest
> and web::logfilter so that subsequent calls with the same arguments
> will not create a new logdest or logfilter respectively.  The clear
> advantage would be that you can define your logging stuff in
> web::initializer, but you also don't have problems if you define
> them in your per request code. In addition, there is no need to
> delete them after a request has finished -> they will still be
> available in web::finalizer (draw back: more work than the others)

> All in all I tend to favor the last approach, but it's more work and
> a bigger change. Is compatibility an issue? Does anyone see a
> porblem?

I agree that it seems like the most correct way of doing things.  Not
having any websh code in production, I can't comment on compatibility
issues though:-)

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: websh-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: websh-dev-help@tcl.apache.org


Mime
View raw message