Note that there are some explanatory texts on larger screens.

plurals
  1. PORobust real-time communication between iOS App and Mac App
    text
    copied!<p>We're working on an exhibit (<a href="http://pulse.media.mit.edu" rel="nofollow">http://pulse.media.mit.edu</a>) and I'm brand new to iOS, objective-c and Xcode. The exhibit deadline is in one week and I'm stuck.</p> <p>The problem I'm having seemed simple enough.</p> <p>Our exhibit has a projector and an iPad. The projector will be hooked up to a mac and be playing a video. The iPad will act as a controller for those videos. More simply:</p> <p>I have 50 videos on a Mac. I need to develop an application on the Mac, that, when opened will loop one of the videos.</p> <p>On an iPad, I need to develop an app that can change between the videos on the mac in real time. The iOS app is already designed, we're just struggling with some code. </p> <p>On the mac, when the iPad tells the Mac to change video, we'd like it to switch between videos using Core Animation, like this (http://youtu.be/pyd8O-2mkgk?t=1m).</p> <p>So my question: What is the most robust way to do this? It has to be able to run in a museum, for two months. Some things to consider: </p> <ul> <li>We are 4,000 miles away and can't monitor it all the time. We'll check nightly to see if it's still working, but it should run the day without breaking. </li> <li>If people unplug the iPad, it should still work.</li> <li>It should be as robust as possible.</li> </ul> <p><strong>How can I best do this? Should I write to a database from the iPad onto a database running locally on the connected Mac and then monitor that database 10 times every second? Are sockets robust enough to use alone?</strong></p> <p>If you do suggest a way, can you please point me in the direction of some resources (frameworks, function names, etc) that can help me do this quickly? </p> <p>Thank you for your time.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload