Sujet : Re: Upcoming time boundary events
De : marc.gr.vandyck (at) *nospam* invalid.skynet.be (Marc Van Dyck)
Groupes : comp.os.vmsDate : 02. Jun 2025, 09:59:15
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <mn.12937e96a0bc3b12.104627@invalid.skynet.be>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : MesNews/1.08.06.00-gb
on 02/06/2025, Lawrence D'Oliveiro supposed :
On Sun, 1 Jun 2025 21:49:59 -0400, Arne Vajhøj wrote:
>
On 5/30/2025 6:41 PM, Lawrence D'Oliveiro wrote:
The irony of it, that the DEC concept requires creating a separate
server process for every client connection,
It doesn't.
Processes are re-used for task to task servers.
>
Hmm. Presumably the process is kept around for a limited time before being shut down.
>
What about multiple concurrent connections? You can’t avoid creating extra processes in that situation.
Yes there is a time out. Mechanism is built in NET$SERVER.COM if I
remember well. I think you can even customize the time out with a
logical name. It can have some side effects, some of which I did not
like. Therefore I used to terminate all my network mode procedures with
a STOP/ID=0 instead of LOGOUT, just to make sure processes would not be
re-used. Process creation used to be expensive on OpenVMS but with
today's hardware it's hardly an issue anymore.
-- Marc Van Dyck