I also have question what is the meaning of changing -ttl
relativeSeconds into -expires absolutetime.
Now Tcl code looks bloated with all -expires [expr [ns_time]+3600] lines
not counting that this is much slower than doing such incrementing C.
May be we can keep both parameters, -ttl as rela
I believe we will have to find some consensus about what and how
we expect this cache stuff to work.
For me, I'm OK with everything, as long as it computes!
Stephen, you are the major moving force behind this module.
Can you get us the direction you'd like to follow and let
us see how we can go t
Am 27.06.2006 um 14:16 schrieb Zoran Vasiljevic:
This might be if the default value of cacheTimeout of 3 seconds
is simply too low for the operation of caching the element in
ns_cache_eval.
I think that this was the problem. So after increasing from 3 to 60
secs, the problems went away.
I be
I agree, it is just sometimes useful to cancel long running Tcl thread
instead of restarting the whole server. It will tell you when it stuck
and you can fix that problem later, it is not for daily use of course.
Zoran Vasiljevic wrote:
Am 28.06.2006 um 19:06 schrieb Vlad Seryakov:
i am porti
Am 28.06.2006 um 19:06 schrieb Vlad Seryakov:
i am porting Tcl Async cancelation from AOlserver 4.5 if nobody
objects,
this is great feature
Hm... I do not object, but why is this great?
The cancellation is always the worst possible thing
you can do. This means that the code is inherently
Hi,
i am porting Tcl Async cancelation from AOlserver 4.5 if nobody objects,
this is great feature
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
