The data sent is actually just some string or Boolean parameters, so Windows applications can perform specific tasks.
Someone will write Windows applications, I will write a Mac application.
I can find information about Mac-to-Mac communication in the developer’s documentation, but nothing about what I need.
The best way to achieve this goal What is the best way? What protocol is best for this?
> #1 is how you discover other applications. Bonjour is a possibility, just like local broadcasting, explicitly configuring the hostname of the peer
>#2 is when you find it and talk to another machine Way. For that part, I suggest:
> a) Use TCP instead of UDP (in most cases), so you don’t have to worry about retransmission & sequencing> b) Not invent your own on TCP Client-server protocol, but use the existing protocol. I heard that something called “HTTP” has become popular…
I need to use Mac OS X Write an application on the above, it will send remote commands to the Windows application to perform certain tasks. The computer will be on the same subnet, and both Mac and Windows computers have fixed IPs.
Data sent It’s actually just some string or boolean parameters, so Windows applications can perform specific tasks.
Someone will write Windows applications, and I will write Mac applications.
The developer’s documentation found about Mac-to-Mac communication, but nothing about what I need.
What is the best way to achieve this? What protocol is best for this?
There are at least two different questions here:
>#1 is how you discover other applications. Bonjour is One possibility, just like local broadcasting, explicitly configuring the hostname of the peer
>#2 is the way you can talk to another machine after you find it. For that part, I suggest:
> a) Use TCP instead of UDP (in most cases), so you don’t have to worry about retransmission & sequencing> b) Instead of inventing your own client-server protocol on TCP, use existing protocols . I heard that something called “HTTP” has become popular…