Am 29.06.2006 um 19:21 schrieb Vlad Seryakov:
Communication between serialized threads doesn't sound like a
cache to me.
Anyway, the idea is that if you need to do weird stuff it should be
possible, and an ns_cache_info equivalent can be writen in ~3
lines of
Tcl.
Very sad.
I'd suggest we define what is weird and what is not first.
I believe Stephen is trying to say that if you use cache module
to save values between two tasks executed by two serialized
thredas, this is kind of unusual "usage".
I must admit that Stephen is right. But, OTOH, we should not
question anybody's usage that deep. If you or Stephen
say that any feature is needed I will simply trust you and
try to arrange myself accordingly. Of course, this is what I
expect from you in return. I will never ask for a feature I
did not think over and am absolutely sure (and can convince you)
that it is better we add it in the core.
Addind something in the code is easily done but we should NOT
forget that we will have to maintain it for years to come.
So, if something can really be done in a small Tcl wrapper
and IS not performance hog I would vote to do it in Tcl.
Otherwise I would be the last to stand in the way to do it
in the C as part of the common core.
Just my 0.2 cents
Zoran
(who tries to keep the ball rolling)
