×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Niels,
Sorry, it was a very long time ago... but, if I recall correctly, the
IBMer who told me it was a bad choice was mostly concerned about
performance. With givedescriptor(), you have to create a job, get its
job id, and then wait for it to start up and receive the descriptor
before the execution thread can move on to handling the next
connection. This, of course, can be a performance concern. By
contrast, if you call spawn() you can continue with other tasks while
the job is starting up. Or, with sendmsg() the data is buffered, so you
don't have to wait for it to be received before continuing.
The other concern is the authority issue that was mentioned at the start
of this thread.
In my experience, anyone using givedescriptor/takedescriptor could save
themselves some development effort by simply using inetd. Most of the
time, they are duplicating what it already does (and, often not doing it
as well as inetd would!)
-SK
On 3/5/2021 6:18 AM, Niels Liisberg wrote:
Somewhere else in this thread says it is a bad idea.
Does anyone have an idea why it is such a bad idea?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
