From: Vlad S. <vl...@cr...> - 2005-12-30 14:45:02
|
I have web applications and server applications running on our server and in my experience so far i always prefer global caches over per-thread cache. If you need something local in long running thread, you can use Tcl global variables to keep state during the processing, even namespace variables. It is just one Tcl interpreter anyway. Just my 2 cents. Zoran Vasiljevic wrote: > > Am 30.12.2005 um 08:46 schrieb Stephen Deasey: > >> >> But I don't know, there may be situations where a per-thread cache is >> worht while and we should add that...? > > > Hm... for a typical web application (whatever that is) where you have > short lived connections, it is not worth the work, IMO. > But if you have a long running operation in a thread, a per-thread > cache seems like a good idea. There you can stuff (and reuse) Tcl > objects w/o shimmering to/from string. > To be honest, at the moment I do not have any need for such thing > but on the general level, an option to create a cache as "global" > vs. thread-private is a powerful functionality. > > Cheers > Zoran > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |