On Monday 30 June 2003 18:45, you wrote:
Just to be clear - we are not explicitly using namespaces anywhere in our
scripts. We are just set-ing local variables, e.g.:
set foo bar
I believe this is standard programming practice with AOLserver. Is it
correct that AOLserver simply abandons
On Tuesday 01 July 2003 10:36, you wrote:
On Monday 30 June 2003 18:45, you wrote:
Just to be clear - we are not explicitly using namespaces anywhere in our
scripts. We are just set-ing local variables, e.g.:
set foo bar
I believe this is standard programming practice with AOLserver.
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
Just to be clear - we are not explicitly using namespaces anywhere in
our
scripts. We are just set-ing local variables, e.g.:
Of course not. But last time I checked (admitedly a long time ago, in
an older 3.x version of AOLserver), local variables still hung around
in the connection thread
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
Greetings,
We have recently corrected a problem with random AOLserver crashes, and now
we are seeing a different problem: ever-increasing memory usage by our
primary application service between restarts. Some of our application
functions require fairly extensive string processing, which is
