No, ns_cache_exists should be kept, it is useful sometimes to check if
the entry there, for read-only caches for example.
It's hard to tell exactly the real problem, once your application is
over 100K lines of Tcl code which implements the whole company's
OSS/backoffice, there are a lot of spe
Yes, it is more convenience but even nsv_ shared variables work the same
way, keep stringified values and objectifies on the return.
We decided to get rid of thread specific caches and keep global ones
only, and at that time i was for it but now i think simple thread local
cache should be in t
On 4/14/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> On 14.04.2006, at 11:58, Zoran Vasiljevic wrote:
>
> > OK. This is the beast:
> >
> > test cache-6.2 {eval ttl} -body {
> > ns_cache_eval -ttl 1 -- c1 k1 {return a}
> > after 1500
> > ns_cache_eval c1 k1 {return b}
> > } -clean
On 4/5/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> Yes, i use cache and in my case i do need to use get and set in
> different situations, for example i need to set cache entry regardless
> of what is there, eval will return me existing value, so i need to flush
> it first which gets to the same
On 4/14/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> Yes, i always use Tcl vars but when i have too many different callbacks
> and filters, using simple mechanism to access named value that is global
> inside the thread make it easier than performing multiple global
> statements over the code. If
