Re: [AOLSERVER] Ever-increasing memory usage?
On Thursday 26 June 2003 21:12, you wrote: Is this required to ensure that memory is reclaimed? I had naively assumed that Tcl/AOLserver would take care of this (that is, that variables created within a connection or procedure would be torn down upon closure of the connection without manual intervention). Is this not the case? This would cover only global vars and file channels, nothing else. Any namespaced variables are not takein in account. Assuming manual reclamation is needed, I expect we would use ns_atclose and implement a procedure which uses [info vars] to collect the names of local variables and unset them (we will need to create an exclusion list of nsv* variables which are never unset). Do you forsee any problems with this approach? No problems. it would be helpful to know which variables are hot spots and only drop those w/o being too general, if the performance is paramount. Cheers Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Oracle Driver Bug Fix
Earlier this month here we were running into an old bug in the oracle driver, described here: http://ccm.redhat.com/bboard-archive/webdb/000Ya9.html In the ns_ora exec_plsql command the return buffer was not being given a null terminator (or, as is the case in other bind calls, completely filled with nulls) after being allocated. I added a memset call so it acts here like in other ns_ora functions that use bind variables, which so far has solved the problem. Perhaps this would be useful for the next release of the oracle driver... (patch below) -- jesse kipp [EMAIL PROTECTED] --- ora8.c~ 2002-10-03 14:05:58.0 -0600 +++ ora8.c 2003-06-24 17:42:17.0 -0600 @@ -3338,6 +3338,7 @@ } buf = Ns_Malloc(EXEC_PLSQL_BUFFER_SIZE); + memset(buf, (int)'\0', (size_t)EXEC_PLSQL_BUFFER_SIZE); oci_status = OCIBindByPos (connection-stmt, bind, -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] can aolserver redirect to a different site
I got this to work:
proc redirect_to_site1a {args why} {
ns_returnredirect http://www.site1a[ns_conn url]
return filter_return
}
ns_register_filter preauth GET /* redirect_to_site1a
I tried trace where preauth is, but it didn't work so I tried preauth
and now it works..
wj
On Friday, Jun 20, 2003, at 09:06 America/Denver, Wes James wrote:
I fixed this up a bit (added trace in ns_register_filter):
proc redirect_to_site1a { why } {
#ns_log notice ns_returnredirect http://www.site1a[ns_conn url]
ns_returnredirect http://www.site1a[ns_conn url]
return filter_ok
}
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of
your email blank.
