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
> 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 copi
4.0.10
J
Jade Rubick
Director of Development
TRUiST
120 Wall Street, 4th Floor
New York, NY USA
jrub...@truist.com
+1 503 285 4963
+1 707 671 1333 fax
www.truist.com
The information contained in this email/document is confidential and may be
legally privileged. Access to this mail/document by
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 A
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
Tom Jackson schrieb:
On Thu, 2009-05-14 at 18:08 -0400, Jim Davidson wrote:
Good idea. Maybe it would make sense to disable it by default with
some config flag to enable?
I was thinking the same, but I wasn't sure how many people actually use
this command.
i would even recommend
