Re: [naviserver-devel] Re: [naviserver-commits] naviserver/nsd tclcache.c,1.2,1.3 tclcmds.c,1.34,1.35

[Stephen D. <sd...@gm...>]

On 4/16/06, Vlad Seryakov <vl...@cr...> wrote:
> No, ns_cache_exists should be kept, it is useful sometimes to check if
> the entry there, for read-only caches for example.

There's no point checking for existence unless you're also going to do
something with it -- that's a separate operation and that's a race
condition.

A read only cache doesn't make any sense to me.  If you're not
entering values at runtime, you're not using the cache feature of
purging which is the only thing differentiating it from an nsv.  Just
use nsv's in this case.

> 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.


It's a trade off.  In this case the problem I have is that these extra
features encourage broken usage.  I really think it's important to
find the real solution to the problem, which I'm happy to help you do.
 I'm not keen to add broken features to the code base because yours is
too big to figure out though.  Hope that doesn't sound too harsh, it's
not meant to be. \