Re: Socket Question

- You might in fact be right that it will work using the spawn API to
initiate the second job. From what I remember having read at one point
though was the requirement of threads to run a full duplex socket (in a FAQ
related to a product claiming to do just that).

But then again, to run a program using threads on the i5 it must be
submitted using the spawn API. So maybe it comes down to what exactly the
spawn API does differently than the other means of initiating a job?

-Carsten

Sorry, I think I worded that statement inaccurate! - I know that a

socket

can be passed from one job to another (using the givedescriptor() and
takedescriptor() APIs), but is it possible for two separate jobs
simultaneously to read from and write to the same socket, respectively?

Hmmm... now you're making me question myself.

I thought it was possible to have the spawn() API create a new job and
pass a socket descriptor to it.  Then, the original job could recv() from
that descriptor, and the spawned job could send() to that descriptor...

For an existing job, I thought it was possible to use sendmsg() and
recvmsg() to accomplish the same thing.

Am I wrong?