By Michael Yoon, Jon Salz and Lars -Pind.
</authorblurb>When using AOLserver, remember that there are effectively two types of global @@ -40,7 +46,7 @@ that would affect (and complicate) our use of script-global variables dramatically, which would then be better described as thread-global variables. -Given AOLserver's behaviour, however, "script-global" +Given AOLserver's behavior, however, "script-global" is a more appropriate term.
ns_schedule_proc
and
ad_schedule_proc
each take a
-thread
flag to cause a
-scheduled procedure to run asychronously, in its own thread. It
+scheduled procedure to run asynchronously, in its own thread. It
almost always seems like a good idea to specify this switch, but
there's a problem.It turns out that whenever a task scheduled with ns_schedule_proc -thread
or ad_schedule_proc -thread t
is run,
AOLserver creates a brand new thread and a brand new interpreter,
@@ -228,8 +234,8 @@
However, when using ns_set get
to perform lookup by name, they perform a linear lookup, whereas
arrays use a hash table, so ns_set
s are slower than arrays when the
-number of entries is large.
($Id: programming-with-aolserver.xml,v 1.9 -2017/12/22 13:23:35 gustafn Exp $)
+number of entries is large.