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 i want to add another var, i need to create
Tcl wrapper so i do not need to go over the code and see where i may use
it, so in this case ns_tls will make it easier. But in general, global
Tcl var is way to go.
Zoran Vasiljevic wrote:
On 14.04.2006, at 18:36, Vlad Seryakov wrote:
This is very subjective but it will make my life much easier and
application more cleaner by using Tls in Tcl, so if nobody will object
i would keep ns_tls command if possible.
Absolutely! I have no problem with that, whatsoever.
It is just that I was curious *when* you start needing
such things, as we never did. We need(ed) thread-wide
things (so nsv_ is ok) but not thread-specific.
Good to know...
Cheers
Zoran
-------------------------------------------------------
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=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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/
