Liste des Groupes | Revenir à co vms |
On 10/6/2024 11:12 AM, Michael S wrote:On Fri, 4 Oct 2024 17:43:02 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <vdp8kn$a67s$1@dont-email.me>,>
Dave Froble <davef@tsoft-inc.com> wrote:On 10/3/2024 7:00 PM, Chris Townley wrote:>[snip]>
I don't remember George, but we have certainly woken up Dave! ;)
>
and I am sure the troll is happy...
I'm not sure whether I've been insulted?
I suspect the "troll" reference is to Lawrence. Sadly, Arne can
not help himself when it comes to resisting arguing with that
clown.
>
- Dan C.
Troll or not, but the question about ability to pass open TCP
socket to child process (or, may be, to unrelated process) under
VMS is a good question.
As a lurker, I am waiting for the expert answer with interest.
Well, some of the issue is in the text of the question. What does
one mean be "pass socket"?
When creating a socket, one can specify it to be shared. What I was
doing was passing the information to a worker process, then letting
the worker process open the existing socket.
So, would that be considered "passing an open socket"?
I can post some of the development code is anyone is interested. I
was working on the inter-process communications when I dropped the
project. I believe I did open the shared socket in the worker
process.
Les messages affichés proviennent d'usenet.