DN>Ok, first of all. You never actually "create" a remote
pipe. You create a
DN>local pipe (ie. the name is like '\PIPE\MyPipe') which can be opened from a
DN>remote workstation (name is like '\\MyServer\PIPE\MyPipe').

DN>JD> sprintf(pipename, "%s.%d", od_control.od_pipe_name,
od_control.od_node);

DN>I'm unfamiliar with your program (I probably should get around to
DN>installing a few doors ;-) I'm not sure what exactly you are doing.
DN>However, what you want to end up with is:

DN>On machine 'sys2': DosCreateNPipe("\\pipe\\oxpipe.0",...);
DN>On the client    : DosOpen("\\sys2\\pipe\\oxpipe.0",...);

I see.  This is helpful information.  The way that my routines work at
this point is that each node creates its own pipe, *but* all pipes are
assumed to be created in the same directory.  (Thus, I assumed that in a
networked environment, they'd all create the pipes on a common server.)

It sounds as if in a peer environment, I could have each node create
its pipe locally, and allow the sysop to specify *all the machine names*
that may run Ox on the LAN so that the door can check each of them for
node pipes.  On the other hand, that would only work if all of the
machines running BBS nodes were configured to act as servers rather than
just clients, right?

The alternative, I suppose, would be to write a fairly simple message
coordinator program that would run on a central server machine and route
messages back and forth between all the nodes.  I've avoided things like
this thus far because they seem to complicate the setup for the door,
but it sounds as if this may be my only alternative.

Thanks for the reply!  I appreciate the "education," and if you have any
comments on the alternatives I was thinking over, I'd very much
appreciate them.

Take care,

Joel

 * OLX 2.1 TD * Roaches... Now *that's* a thought...

--- WILDMAIL!/WC v4.12