But for nsv shared variables you *have* to stringify because Tcl objs can not pass between threads. Here your explicitly looking for thread local, so stringifying would seem to be an unnecessary slowdown.
Mostly we store strings in the cache so it is not a real problem
This isn't a cache, there's no eviction policy.
But if i do not need eviction policy, if i want to keep them forever?
I don't see how ns_tlsthis isn't exactly equivalent to: set ::tcl_MyMache Whatever which has the big advantage of keeping Tcl objects in object form.
True, and i am still using it this way, i even use global arrays to be able to get all values easily. But i have a lot of filters and callback procedures that are called from different places even from C modules. Calling Tcl wrapper all the time is a big slow down especially if i need to process several hundreds of rows, tls will be a big improvement in this case.
But i agree that functionality-wise it is the same -- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
