Question

I am trying to plan out a few iOS/server apps for internal use. On the iOS side I’ll use Core Data, but I’m not so sure what many people do on the server side. I will be running a Mac Mini with OS X Server 10.6.X. This app will need to sync when the iOS device is on the internal WiFi as well as over 3G. Some of this data will need to be accessed by the company’s external web site which is written in PHP, as well as by native apps on iMacs internally. Should I just use a MySQL db on the server, and expose a web service, or is there a better way by using Core Data on the server that would make syncing the iOS device easier? The data is not too relationally complex. I’m thinking tblClient 1->M tblJob 1->M tblImage/Drawing.

Answer 1

In most cases, the server side doesn’t matter because your communicating with URLs and some standard data format like JSON.

You can connect to a remote Core Data store but it doesn’t handle multiple access so there’s seldom much point to doing so. You could write your own server that uses Core Data but usually its quicker and easier to use a preexisting package dedicated to server work.

My advice is to go with the server that is quickest and easiest for you to implement and maintain with the knowledge and tools you have on hand. It’s easier to adapt the client side Core Data to inputs from the server than it is to attempt to integrate Core Data directly into the server.