> To access multiple files, use sharing.  One option is sopen - not ANSI, 
 > IIRC, but available in many compilers (Watcom included).  The other option 
 > is to use DosOpen directly (I would recommend writing some sort of io 
 > library to go with it just in case you want to port to AIX or something - 
 > then you just rewrite the library rather than everything else).

There's only one thin with this sharing stuff. In read-only mode it's okay, 
but not if data are to be written. And as you mentioned DosOpen (I think 
too...) can w8 for a file to become avaliable if it's not. But the problem 
then would be that if an other thread/proccess accesses the file and locks up, 
the file will be locked for ever - causing the BBS to hang. But in the other 
hand I'd be better do do my own loop instead of letting DosOpen handle it.

But this C/S thing. So what you mean is that I should 'create' a file that the 
client reads directly through the server via a pipe? Let's see, pipe can be 
read via DosOpen, right? I don't remember, but if so that's the perfect 
solution! If a node wants to write data, then the server could create a temp-
file, and when the client closes the file, the server could write the data to 
it. That's perfect! Only it takes up resources, but I'll have to doo. It 
won't be easy to hang the BBS as long as I make the server stable as hell. I 
think I'll go with that unless you have another opinion maybe?

Thanx!

/ Peter Schuller   [TeamOS/2]   petersch{at}kuai.se
 

--- AdeptXBBS v1.08a26 (VC) (Registered)