I guess if it's thread safe now, the ticket should be closed with a reference to aolserver 4.5.
2009/5/16 Jim Davidson <jgdavid...@mac.com> > Hi, > > I'm looking at the head code and it appears it's now safe -- the connection > list is walked with a pool lock held and the request data (method, url) seem > to be copied with a global "reqlock" mutex held. > > Jade: What version of AOLserver are you using? > > > -Jim > > > > > On May 15, 2009, at 10:06 AM, Tom Jackson wrote: > > One thing which would be nice is to put the Tcl API into a module which >> as to be loaded, and keep the C API available in the core. It is >> obviously more work, but the admin has to make a choice to load the Tcl >> API, which is more open to misuse. I did something like this for a few >> additional ns_conn options. >> >> Gustaf's idea is easier to pull off at least initially, but it shouldn't >> be tied to an unrelated option like debugging. I leave on debugging for >> low traffic servers and I can also turn it on/off on a per-namespace >> basis. >> >> tom jackson >> >> On Thu, 2009-05-14 at 15:48 -0700, Sep Ng wrote: >> >>> How about having the proc enable only if debug settings are turned on >>> on AOLserver? >>> >> >> >> -- >> AOLserver - http://www.aolserver.com/ >> >> To Remove yourself from this list, simply send an email to < >> lists...@listserv.aol.com> with the >> body of "SIGNOFF AOLSERVER" in the email message. You can leave the >> Subject: field of your email blank. >> > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to < > lists...@listserv.aol.com> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > -- "A scrum a day keeps the pigs at bay" -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
