* now by default Gateways DO NOT SPAWN execution threads
you can call "remote_init_threads(NUM)" on an already instantiated
gateway, which will install a loop on the other side which will
dispatch each execution task to its own thread.
* execution is dissallowed on the side which initiates a gateway
(rarely used, anyway)
* some cleanups (hopefully)
--HG--
branch : trunk
messages by having threads die more silently. Most
of these threads and tracebacks are anyway on some
remote machine, and we need to take care that errors
are routed to the place of invocation (e.g. the
remote_exec() invoker should get remote exceptions,
if the remote thread goes out of scope, the resulting
exception will not be seen likely, anyway)
--HG--
branch : trunk
from the sendqueue, then trigger the queue
to shutdown. (This is an attempt to get
rid of the still appearing "exception in thread"
messages)
--HG--
branch : trunk
hpk