Re: Core Data Multiuser
Re: Core Data Multiuser
- Subject: Re: Core Data Multiuser
- From: Kyle Sluder <email@hidden>
- Date: Mon, 08 Oct 2012 09:52:49 -0700
On Mon, Oct 8, 2012, at 08:40 AM, Flavio Donadio wrote:
> Hello, all!
>
>
> This a follow-up to a thread started last July. I looked into a lot of
> things, tested some crazy ideas (that went wrong) and came to my final
> decision for my project. I consider it very important to let people know
> what I decided. Maybe I can help someone. And, for sure, you guys can
> warn me if I'm making the wrong decision.
>
> I can say, for sure, that sharing the SQLite database is a bad idea if
> you have a busy and slow network. The Distributed Objects idea is not so
> bad, but gives a lot of headaches: the implementation of your
> "business-logic" ends up being composed of 90% error handling code.
>
> I also dismissed the "real-time updates" idea. The user will have to
> refresh the view manually. It saves a lot of effort and users will not
> get confused by table views changing unexpectedly, for example.
I agree with all of your decisions.
> So, for the back-end (server side), I'll be using WebObjects to develop a
> RESTful web service. I chose WebObjects because it's proven, it works
> very well (Apple uses it on their app stores and iTunes) and it uses a
> language that is kind of familiar to me (being used to PHP and a couple
> of C variants). Also, the framework's design patterns are very similar to
> Cocoa. The development tools are good enough and try to mimic the old
> tools that Apple provided. It can be deployed on Mac OS X, Linux and
> others, using standard Java application servers. The WO community seems
> to be very strong, united and helpful (just check how busy the
> webobjects-dev list is today).
We still run WO 4.5 to power our own store, but we go through some major
hoops to do so.
Personally, I'd be inclined to choose a more stable and up-to-date
technology, but I'm not a server-side programmer.
> For the front-end, I'll develop a Cocoa client using ActiveResourceKit
> (https://github.com/royratcliffe/ActiveResourceKit). From what I've seen,
> it's the most straight forward to use, and the most feature-complete
> framework for consuming RESTful web services.
Have you heard of NSIncrementalStore? If you can target Lion and iOS 5,
you can continue to use Core Data on the client while communicating with
whatever backend and over whatever protocol you choose.
Good luck on your project.
--Kyle Sluder
_______________________________________________
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