Re: EOF (was [objC retain];
Re: EOF (was [objC retain];
- Subject: Re: EOF (was [objC retain];
- From: Chris Hanson <email@hidden>
- Date: Fri, 29 Mar 2002 19:21:59 -0600
At 11:23 AM -0500 3/28/02, Bill Bumgarner wrote:
Of which, EOF sucks for general object graph persistence unless your
object graph is connected by nothing but direct relationships and
arrays.
If all you have is a hammer, all the world's problems start looking
like nails...
The thing is, for lots of applications -- whether consumer desktop
applications or custom n-tier applications -- the problems are
sufficiently nail-like that EOF wouldn't suck.
Is it the best solution in every case? Not necessarily. But many
applications need the ability to manage interrelated objects, perform
various types of simple queries and sorts, and deal with object
graphs that can't always be fully resident in memory (unlike a
property list or archive). EOF deals with these cases well.
In fact, I'll go so far as to say that EOF makes developing the model
side of an application as easy as Interface Builder and AppKit make
developing the view side! And just like AppKit, it's a *great* start
and great for the most common case. Also just like AppKit, it won't
do absolutely everything for you; if you have more complex needs,
you'll have to do more work, but it'll make that work fairly
straightforward and elegant.
Others have commented the native drivers issue, but I'll throw in my
two cents: A flat-file adaptor is necessary, a JDBC adaptor would be
great (but could be done by a third party, though it'd be better if
it came with EOF), the Mac OS X database vendors would likely ship
adaptors in short order, and the developer community would likely
create adaptors for Open Source databases in short order.
ObPlea: If you want database access in Cocoa, please file a bug
report at <
http://bugreport.apple.com/>. If you can, be as specific
as possible and give as detailed a business case -- for your business
needs -- as possible so Apple can best prioritize their development
efforts and decision making. But if you can't be that specific,
don't let that hold you back from communicating what you can. (I
know I've been saying "Be specific!" lately, and I think that's the
best strategy, but saying "Please bring back Cocoa EOF!" is better
than saying nothing at all.)
-- Chris
--
Chris Hanson | Email: email@hidden
bDistributed.com, Inc. | Phone: +1-847-372-3955
Mac OS X & WebObjects Consulting | Fax: +1-847-589-3738
http://bdistributed.com/ | Personal Email: email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.