Brett Schwarz schrieb:
Just curious...did you have to do anything special to get it working inside
aolserver?
There are two ways of using tcl libthread in aolsever:
(a) configure it for plain tcl (standard), load into aolserver with
"package require";
you get tsv:: etc.
(b) configure with "--with-aolserver", load it as an aolserver module
from the startup script;
in this case libthread overloads nsv etc.
with (a) you have the advantage with standard tcl compatibility, with
(b) one
can run existing aolserver applications (OpenACS, ...) on it, still
getting the
performance gain, and - for me the most important benefit - you get
threads that can easily communitcate via the event-loop used in the tcl
thread
library.
-gustaf neumann
----- Original Message ----
From: Jay Rohr <[EMAIL PROTECTED]>
To: AOLSERVER@LISTSERV.AOL.COM
Sent: Wednesday, April 16, 2008 2:17:38 PM
Subject: Re: [AOLSERVER] ns_share (was Active participation)
just FYI
I am using the tsv (from the thread package) functions within aolserver
and, at least for my uses, it is faster than the nsv equivalents. (and
it is a namespace :-)) It also has a number of advantages, I can run
the same code outside of aolserver, the tsv::lock allows me to run a
block of code under the shared mutex, and it has a more complete set of
list functions.
Jay
Jim Davidson wrote:
Hi,
Brent Welch wrote some ns_share code which worked with Tcl variable
traces to emulate the original code. It works except for a few edge
cases but is generally considered less efficient and flexible than the
new nsv_* commands. So, when I say we gave up on ns_share I mean we
stopped applying our patches to the Tcl core for ns_share, allowing us
to use the Tcl source un-altered.
-Jim
On Apr 14, 2008, at 1:37 PM, Brett Schwarz wrote:
True -- the original threading in AOLserver 2.0 way back in 1995 (yes,
1995) was based on a thread-safe hacked Tcl 7.3. I can't recall where
I got it -- I think someone at UCB did the work. We later hacked Tcl
7.4 and 8.1 on our own before enough support was in the Tcl core and
we were ready to give up on "ns_share" which was a significant hack
that couldn't reasonably be brought forward.
I was just looking at file.tcl, and it still uses ns_share. Is that
ok? Or should that be changed?
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
