Tom Stelter ([log in to unmask]) wrote:
: We have done a prototype of this but now need to address security,
: mutli-threaded access, etc.  Are you forking numerous processes to handle
: this?  Or does your batch job single-thread all the incoming requests?  If
: so, do you have any queueing mechanism for the requests or any routing of
: the responses built in?
:  ----------
 
I was speaking hypothetically.  If I were designing it, it would probably
be a batch job, single-threading the requests.  Of course, with the POSIX
shell, and the fork mechanism, it would be possible to have a listener
task that would launch a child process to handle each separate request that
came in.  There are numerous ways this could be accomplished.  I was just
trying to point out that message files were not the only way to go.
 
 
DISCLAIMER:  I am not making a statment for my employer.  This is just my
             own opinion.