• 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: MySQL and Cocoa - looking for samples, kits, docs, etc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MySQL and Cocoa - looking for samples, kits, docs, etc


  • Subject: Re: MySQL and Cocoa - looking for samples, kits, docs, etc
  • From: Chris Hanson <email@hidden>
  • Date: Wed, 27 Dec 2006 16:03:56 -0800

In addition to what other posters have said, consider the goals of your application.

If your goal is to simply create a data-oriented desktop application, I'd strongly recommend using Core Data. That way you won't have to deploy a client-server database as part of your application. On the other hand, if your goal is to create a large network-oriented multi- user application with a desktop component, a client-server database might be more appropriate.

The dividing line between the two cases -- single-user or networked multi-user -- can be fuzzy as well. For example, you can use Core Data with an SQLite persistent store located on a shared filesystem to implement workgroup applications so long as the shared filesystem supports appropriate file locking and/or you won't have a lot of users writing to the database at once. (Lots of simultaneous writes and deficient file locking can both significantly degrade performance; this is true for any shared-filesystem technology.)

Another approach to developing client-server applications for Mac OS X is to use Core Data on the client side to manage the object graph representing data retrieved from and to send to the server, and to use web servers (whether XML-RPC, SOAP, or REST/document-based) to communicate between the client and server. This way I can abstract the interface between the client and the server -- rather than rely on sending raw database queries and result sets back and forth -- and also achieve the scalability benefits of avoiding a shared filesystem.

Which category of application above best describes your development goal?

  -- Chris

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >MySQL and Cocoa - looking for samples, kits, docs, etc (From: "Smith, Steven (RSAA Storage)" <email@hidden>)

  • Prev by Date: Re: NSBezierPath from NSImage
  • Next by Date: Re: How can I tell if a port is already being used?
  • Previous by thread: Re: MySQL and Cocoa - looking for samples, kits, docs, etc
  • Next by thread: 'Duplicating' a section of an NSView...
  • Index(es):
    • Date
    • Thread