=== Gregory Woodhouse [EMAIL PROTECTED] "The most profound technologies are those that disappear." --Mark Weiser ------------------------------------------------------- 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_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Okay, just one more response. When you get right down to it, the
point I was trying to make is that polling in basically I/O (even if
the "device" you are reading is shared memory) and I/O is expensive,
much more so than most people (including programmers) realize. The
nice thing about asynchronous I/O (not supported in standard MUMPS)
is that it eliminates the need for "almost busy" waiting, and instead
uses asynchronous notification mechanisms (like signals) to notify a
process when a device has become ready. This is not exactly the same
issue, but trying to read from a socket periodically in hopes that
data will be available is particularly bad.
- Re: [Hardhats-members] Changeing/Activating PORT 9200 on... Gregory Woodhouse
- Re: [Hardhats-members] Changeing/Activating PORT 92... Chris Richardson
- Re: [Hardhats-members] Changeing/Activating POR... Gregory Woodhouse