MFC app with iPhone

[Software2007]

I have a simple MFC data acquisition app that runs on windows. I wanted to make a small iPhone/ipad app that talks to my windows app every 10 msec or so. Equivalent to what you would do with pocketPC thing. I just need to send simple text file with some simple commands so both sides can see the commands and act upon it. I am not sure how do I go about sharing a file between the 2 sides? iCloud? ..etc? Any ideas or someone with similar experience? Thanks

[Code o mat]

Software2007 wrote:

I wanted to make a small iPhone/ipad app that talks to my windows app every 10 msec or so.

this indicates that you want the iOS app to upload that file to your MFC app.

Software2007 wrote:

I am not sure how do I go about sharing a file between the 2 sides? iCloud?

this indicates that you want to have both sides accessing the same content (file) practically at the same time. Which is it? If it is the first situation, then i guess HTTP should work.

> The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<

[Software2007]

It is more like the second. I would like to send commands between the two sides via a text file, or it could be two text files, win_to_ios.txt and iOS_to_win.txt. The point is how and where do these files go so that both sides can be looking at the file(s) of interest? For instance, on the iPhone side, I might have screen with buttons a,b,c, when 'a' is pushed I would like to write 'a' to some file, the MFC on windows would look at this file every 10 ms , would read the 'a' and launch a missile. I know, I wouldn't be launching a missile every 10 ms :)...I understand this has to be a shared network thing, but I was just wondering what would be the easiest solution since this is nothing but sharing a text file.

[Albert Holguin]

Your best bet should probably be to look up inter-process communications[^] and pick one that fits your situation best. If you have two different systems with two different operating systems, your best bet is to use sockets.

[Code o mat]

But why a shared text file? Is there some particular reason for that? As i see it this would work fine with simply using a TCP/IP connection or UDP or somesuch to send and receive commands, don't know what is available under iOS though. Anyways, if you do insist on the shared file thing then you could try looking into a samba implementation (or there was some kinf of web-based file share protocol, but can't recall the name, webdev or something similar), i have seen software using samba on iOS so that should be possible (maybe there are libraries for it?).

> The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<