Re: Disadvantages of Bridging Java in Objective-C Cocoa Apps
Re: Disadvantages of Bridging Java in Objective-C Cocoa Apps
- Subject: Re: Disadvantages of Bridging Java in Objective-C Cocoa Apps
- From: Eric Czarny <email@hidden>
- Date: Tue, 4 Feb 2003 17:20:30 -0500
On Tuesday, February 4, 2003, at 04:41 PM, June Van Dyke wrote:
On 2/4/03 7:01 AM, "Eric Czarny" <email@hidden> wrote:
I was just curious if there
are many disadvantages to using Java classes within my Objective-C
applications to, for instance, utilize the XML-RPC classes written by
Apache.
Well, loading Java is slooooooow. Look at LimeWire. Granted, since
most of
your app would be Obj-C, you'd get OK speed once running, but it will
take
anywhere from three to ten seconds to load Java (and thus your app).
Unless you have a very good reason, I'd suggest you don't use Java,
for the
end-user's sake (and to reduce debugging times :p).
Thanks for the advice! I would like to find another way in which to use
XML-RPC in my application; however, the article I read on Cocoa's
XML-RPC functionality didn't provide nearly as much information as I
would have hoped for, I did run into an Objective-C library but I am
just not entirely sure how to utilize it. I'm rather new to
Objective-C, as well as programming for real-world applications (ap
computer science in high school just doesn't give you the necessary
information). Would I download the source of the library, compile it
and link it into my own code? Any help would be greatly appreciated...
I hope to write a Cocoa front-end to my future PHP web-logging
software. Once again, thanks in advance!
Best Regards,
Eric Czarny
http://www.laterus.net
_______________________________________________
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.