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 specific tasks i have to solve.
The more flexible and feature rich API is the easier the task is.
Stephen Deasey wrote:
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 race condition issue.
Same with get, i just need to get value if it exists without issuing
exists first and then eval, if it is not there i do not want to set it,
eval will set it.
So ns_cache_exists is redundant? Can we remove that?
What's the real problem your solving here? Do you have some custom
code for invalidating cache entries or something?
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
