• 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: State of Cocoa adoption
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of Cocoa adoption


  • Subject: Re: State of Cocoa adoption
  • From: Jim Rankin <email@hidden>
  • Date: Fri, 14 Mar 2003 21:15:59 -0500

On Thursday, March 13, 2003, at 09:13 PM, Andy Satori wrote:

(1) A Cocoa framework for Data Access. Having the ODBC Manager is a step in
the right direction, but gimme a framework to use it with. There are a
couple of third party tools for this, but in this instance, it really needs
to be an NSObject style framework (IMO)

EOF EOF EOF EOF EOF!

But Apple won't let you have it. :)

Seriously, this technology is all Java now in WebObjects, and there's kind of a Cocoa/EOF project type if you install WO, but there's some kind of major licensing restrictions (I always forget what, exactly), to make sure it isn't actually useful for anyone.

Originally, Enterprise Objects Framework was an Objective-C technology. It was and is, even in its Java incarnation, the greatest data access framework in the history of Earth. Search the archive for this list or the Omni WODev list for flamewars about why Apple should/shouldn't bring this back for ObjC.

In the meantime, we should probably all file a bug once a week at bugreporter asking for this to be brought back until Apple does it just to get us all to shut up :).


(2) A Cocoa framework for XML and XSLT. Let's be honest, the business world
is enamored with XML, and I rather doubt that's going to change for a couple
of years.

I'm toying with some ideas for Cocoa XML tools right now. What kinds of functionality do you have in mind, exactly?


I'd love to see a fully interoperable SOAP and XML-RPC toolkit, preferably
Cocoa style, rather than having to mix Carbon API's, that took into account
that the Microsoft implementation is broken, and still works. Of course, I
also wish that Apple would actively get involved with the Mono project to
bring C# and the .NET runtimes to OS X, as it would pave the way for an even
broader developer base.

Does anyone know if the WO SOAP stuff is better than the Cocoa/Carbon stuff?

I keep plugging though, and I've now implemented a couple of my internal
business needs in Cocoa, instead of using Delphi or C++ (ATL VS.NET) with
great success. These tasks are limited though, since the only path to my
Oracle and SQL server databases is via the Java bridge and JDBC, and the
performance impact of that. So for the moment, I use the tools that suit a
job best, and that means that a lot of what I do remains on Windows, because
of the lack of tools.

Hmm, unfortunately EOF is now based on JDBC, so maybe it's not what you're looking for, performance wise.


Andy Satori


Best,
-jimbo
_______________________________________________
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.

  • Follow-Ups:
    • Re: State of Cocoa adoption
      • From: petite_abeille <email@hidden>
References: 
 >Re: State of Cocoa adoption (From: Andy Satori <email@hidden>)

  • Prev by Date: Re: Trouble with a save panel
  • Next by Date: Newbie question - Leak in NSDictionary
  • Previous by thread: XML-RPC toolkit (was Re: State of Cocoa adoption)
  • Next by thread: Re: State of Cocoa adoption
  • Index(es):
    • Date
    • Thread