Re: Core Data Multiple User question
Re: Core Data Multiple User question
- Subject: Re: Core Data Multiple User question
- From: Nate Friedman <email@hidden>
- Date: Fri, 24 Jun 2005 09:18:09 -0700
The Problem with WO is that I don't want to also learn Java. I'm
happy with Objective-C, and if WO was still Obj.C based, I'd probably
take this route. Since I'm not bothering with Java, I'm going the SQL
route. I have the same advantages that WO has in that I can easily
write a web front end (in PHP) that'll interface with the exact same
database.
Thank you for the suggestion though. In the future when I feel like
learning Java, I might just use WO.
- Nate
On Jun 24, 2005, at 7:56 AM, Bill Bumgarner wrote:
Use WebObjects. There are a number of possible solutions, from there.
(1) WebObjects standalone with a Web or Java Client user
interface. Direct 2 JavaClient is also a wonderful and flexibly
means of building clients.
(2) WebObjects using Direct to Web Services to create the server
side. Then, use wsmakestubs to turn the resulting WSDL into
Objective-C classes that can be used directly in your Cocoa
application to talk to the server.
(3) Same as (2), but use the Objective-C client classes to populate
a Core Data in-memory store such that you can leverage Core Data's
undo/redo support, validation, and other features.
In all cases, WO would allow you to easily mix in standard web
based HTML content as a management or monitoring application.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden