In article
<64beb5d4-a5dd-458f-beec-15dc6a7e1f7f@[EMAIL PROTECTED]
>,
eric <eselk@[EMAIL PROTECTED]
> wrote:
> If I have an app running on a Windows PC that is listening for clients
> on a named-pipe (CreateNamedPipe in Win32), is there any way for a Mac
> client to connect to that pipe? From what I can tell, named-pipes on
> Windows and Mac are very different things, and are not compatible at
> all. In the Windows world I know they use special SMB packets, so I
> imagine one could build an SMB packet in this format and send it over
> TCP or whatever protocol you wanted, but I imagine that would require
> a lot of work.
>
> I could make my Windows app listen on a TCP/IP socket.... I'll
> probably go that route, if I have to.
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. Macs have built-in sup****t for afp, smb,
nfs and WebDAV file sharing, ftp read-only, all of these bottom out on
tcp/ip packets.
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.
|
