"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| I'm not a programmer, the only experience comes from some simple
| porting I've done. But I think there are of course sockets and at least
| the OS/2 API has (named) pipes with extended functionality.
|
| The issue here being networked access to and modification of files by
| work groups:
|
| There are indeed security problems; all implementations, I can think
| of, use password protection for file access/modification on a dedicated
| server or peer with server functions.
|
| But please, experts to the front here.
I am not sure if you know the difference between UNIX sockets and BSD
sockets. BSD sockets is used for networking and accessing computers
and otherplaces in the network, when you connect to a BSD socket you
connect to a ip number and a port. UNIX socket on the other hand is
more similar in functioniality to named pipes, but all the semantics
are similar to BSD sockets, so for UNIX socket you connect to a
filename and if you don't have access to that file, bad luck on you.
For the programmer there are no or small differences between BSD and
UNIX sockets (except for the connect). Where named pipes only can
communicate (sanely) with only _one_ program at a time, sockets can
communicate with as many as you wish. For us this means that you can
have several progs using the lyxserver at the same time without
stepping on each others toes.
Lgb
