On Apr 18, 2:22=A0pm, David Phillip Oster <os...@[EMAIL PROTECTED]
> wrote:
> Mac (and traditional Unix) named pipes are in the name space of a local
> file system. For inter-machine communication, you should have a server
> listening on a TCP/IP ****t. =A0Macs have built-in sup****t for afp, smb,
> nfs and WebDAV file sharing, ftp read-only, =A0all of these bottom out
on
> tcp/ip packets.
OK, I'll have to use TCP/IP then. Not a huge switch from named-pipes,
but if I could have used named-pipes (as they work in Windows), then I
would have.
> Which one you choose depends on what you are doing. For database
> activity, none of these are appropriate. You'd be better off with a true
> database that sup****ts clients over the net, like MySQL or Postgres.
By "none of these" I assume you mean AFP, SMB, NFS, and WebDAV....
since TCP/IP itself is fine for DB. I wish it was easy for us to
switch to MySQL or another popular database, but it isn't.
|
