Sure, currently i am using global Tcl vars to store thread data but over
the time code that supports this became kind of ugly, too many things i
need to store during the connection lifetime, i tried multiple
variables, then global array but for example in C, i use Ns_Tls and this
works very good, so i kind of wanted to have the same functionality in
Tcl as well. For one simple var global Tcl is fine but my application is
very big right now and i had to create the Tcl wrapper around accessing
global Tcl vars/arrays from different procs and namespaces. Using Tls
would simplify this and make it very transparent when i want to access
thread specific global data.
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.
Zoran Vasiljevic wrote:
Hi Vlad,
Just out of the curiosity... what you need that
beast for?
Why just not address some global array or such?
Tcl interp is per-thread anyways so you get
this for free.
Obviously there is some hidden usage otherwise
you would not go to that extent. Can you share
it?
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/
