TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Pete Lyall 76703,4230 (X)
from: Niels Peter Bogholm 100566,2262
date: 1995-03-26 06:20:34
subject: #20860-#OS-9 Networking

#: 20866 S12/OS9/68000 (OSK)
    26-Mar-95  06:20:34
Sb: #20860-#OS-9 Networking
Fm: Niels Peter Bogholm 100566,2262
To: Pete Lyall 76703,4230 (X)

Hi Pete,

First some backgroundinfo: My "slave-servers" do manage different VME-Boards
(vacuumcontrol, highvoltage, comm with external robots,..). The slow
communication
(unix-clients or other servers) is realized over network and realtime-comm
between servers on same host with shm. Many servers have a control-loop they
must exec cyclic  (checks pressure, voltage,..).
My solution uses a seperate "network-IO-process" for every server. This waits
for network-actions, does all the communication and then notifies it's server
with events and shm (data). This is fine(usable) for now, but may not be useful
for later projects.

Did your master/slaves share the socket-fd's ?
If yes did you use close,dup,fork (well MW fork isn't a fork (unix!) but a much
slower fork+exec) or did you find a way to share global fd's ?
Do you know if it's  possible to let the system signal an event when a
connectionrequest(!) arrives (cause then one could use ev_wait instead of
accept and this open a hole new world of possibilities..)?

Niels.  

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.