• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OS + iOS best practice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS + iOS best practice


  • Subject: Re: OS + iOS best practice
  • From: Jens Alfke <email@hidden>
  • Date: Fri, 03 Jun 2011 16:07:20 -0700

On Jun 3, 2011, at 1:29 PM, Evadne Wu wrote:

> As for the SQLite file, I am never sure if Core Data’s OS X implementation and iOS implementation share the same format and will continue to be so

SQLite’s file format is 100% consistent cross-platform. And I have no reason to think the same’s not true of CoreData’s schema, since it’s supposed to be compatible between OS’s.

> Note that Dropbox exposes directory hashes, so that might help with images.  I’m not sure if referenced images would be updated at all — this can be a big problem if they can be updated outside the app and you need to handle that.

If you make the application’s store a directory and put the images in it as well as the CoreData file, and if you sync the whole directory with Dropbox, it should Just Work.

> For the record, going with Dropbox might not be very safe, could be not scalable at all, and might have security implications as Jeffrey pointed out.

Dropbox has been quite safe and scalable in my experience. I’ve been using it for a lot of my data for two years, have never lost data or gotten files messed up, and I can’t think of the last time it didn’t sync in a timely manner.

The security issues are overblown due to the recent fracas. Yes, your files could theoretically be accessed by their employees or requested by the FBI. The same thing is true of your email, your iDisk, your Google Docs/Sites/Spreadsheets, any software running on your hosted web space, and anything else you put up in “the Cloud”.

If you’re super paranoid you can encrypt and decrypt the files locally; but then you run into the complications of key management and transfer … which is one of the reasons cloud services don’t go as far as to do this.

> But it might work very well for your scenario.  If you’re serious about making it robust, I still recommend that you create a tiny and dedicated web service for this app…

I understand your point, but in practice, a service designed and run by professionals is going to be more reliable than a quickie web-app cobbled together in your spare time. (What’s the least reliable blog site I’ve ever used? The private WordPress installation I run on my domain. Mostly because the @*%$ sysadmin [me] never has the time to upgrade or fix it…)

—Jens

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >OS + iOS best practice (From: Amy Heavey <email@hidden>)
 >Re: OS + iOS best practice (From: John Joyce <email@hidden>)
 >Re: OS + iOS best practice (From: Amy Heavey <email@hidden>)
 >Re: OS + iOS best practice (From: Evadne Wu <email@hidden>)
 >Re: OS + iOS best practice (From: Amy Gibbs <email@hidden>)
 >Re: OS + iOS best practice (From: Evadne Wu <email@hidden>)

  • Prev by Date: Re: OS + iOS best practice
  • Next by Date: Multi-OS API Question
  • Previous by thread: Re: OS + iOS best practice
  • Next by thread: Re: OS + iOS best practice
  • Index(es):
    • Date
    • Thread