So, in other words, unless you are using Cache, you need to rely on
some external application, or (at least) operating system dependent
mechanism to handle multi-threaded TCP. The only reason Cache is an
exception is that it implements a nonstandard extension to the JOB
command. I think that's basically what I was saying.
To put it a little differently, I didn't mean to imply you couldn't
support multi-threaded TCP (albeit awkwardly, IMO) on MUMPS based
systems, only that you can't do it *in* MUMPS.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"It is foolish to answer a question that
you do not understand."
--G. Polya ("How to Solve It")
On Aug 2, 2005, at 5:48 AM, Doug Martin wrote:
Actually, multithreaded TCP listeners are possible under DSM, MSM,
and Caché. I'm not sure about gtm. DSM supports this through a
VMS service called UCX. MSM supports it through an MSM service
called MSERVER. In both of these models, the service monitors the
specified port and hands off the socket connection to a specified
entry point. Caché supports this capability natively through
extensions to the JOB command by handing off an active TCP
connection (obtained through use of normal M I/O commands) to a
subprocess.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
