• 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: Core Data Multiuser
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data Multiuser


  • Subject: Re: Core Data Multiuser
  • From: Flavio Donadio <email@hidden>
  • Date: Mon, 16 Jul 2012 20:11:14 -0300

On 16/07/2012, at 18:39, Jens Alfke wrote:

> In my experience — and yes I have tried it — using DO between multiple computers is a nightmare. I know it sounds so simple and appealing, but that's because it tries to sweep all the hard problems of networking[1] under the rug. The problems remain, and will bite you, hard.
>
> [...]
>
> The bad news: Approach #1 is straightforward but means you have to abandon Core Data on the client, and design and implement your own network protocol, which is time-consuming. Approach #2 is lovely when it works but I assure you from experience that synchronization is very, very difficult to implement from scratch.

Well... This is one of the more down-to-earth arguments about why I should steer away from this technique. Coming from you, Jens, I can't ignore it.


> I hate to make this post sound like an ad, but I'm developing (for my employer, Couchbase) a framework that implements #2. It's based on CouchDB[2], a very popular nonrelational ("NoSQL") distributed database that is really, really good at synchronization. My framework, TouchDB,[3] lets Mac or iOS or Android apps store databases locally, operate on them locally, and then replicate in real time with a CouchDB server. If there are multiple clients syncing with the same server, it's exactly the solution #2 I outlined above.

I've just took a look at the links you sent and I'm downloading TouchDB. I'll have a careful look at it soon.


> Now, TouchDB isn't compatible with Core Data. But it does have a pretty solid Cocoa API that has an object-model layer a bit like a simplified Core Data. The people who've been using it like it a lot.

To be honest, I know a little about Cocoa and can write almost any simple app you can imagine. Core Data is not, by any measure, a simple framework. I think I understand it, so it feels comfortable for me to try and stick with it. But it doesn't have to be Core Data. It must be Cocoa, though.


Cheers,
Flavio
_______________________________________________

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


  • Follow-Ups:
    • Re: Core Data Multiuser
      • From: Jens Alfke <email@hidden>
References: 
 >Core Data Multiuser (From: Flavio Donadio <email@hidden>)
 >Re: Core Data Multiuser (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: NSTextAttachment
  • Next by Date: Re: Core Data Multiuser
  • Previous by thread: Re: Core Data Multiuser
  • Next by thread: Re: Core Data Multiuser
  • Index(es):
    • Date
    • Thread