On 21.04.2006, at 9:51 Uhr, Frank Herzog wrote:
As I see it, in WO, I can either choose between a Java Client application, or a Web application which is accessed through a web browser.
Additional you can use WebServices to communicate with a Cocoa application. Be prepared to have a lot of traffic between the app and the server when you have long lists or big objects. Also you will run into a good bunch of optimistic looking failures when a couple of users work on the same data.
Perhaps AJAX may a not soo bad idea to get the interactivity to the user and the direct connection to the server.
It all depends on your problem and the typical usage patterns. I have learned in the past that users are happy with a simple web interface if it works as expected.
Or, to put it in other words: I've read that WO is the technology behind the iTunes Music Store. The iTunes application itself is pure Cocoa, I guess. But what is actually connecting the two?
XML. Not sure whether it's a WebService (SOAP).Keep in mind: asynchronous work on shared data by a couple of users on large dataset and a Cocoa app displaying/editing the data will:
- give you HEAVY network traffic, - drive you into a lot of locking handling, - makes the whole dev process much more complex,- make you mad because you have to handle a lot of WebObjects AND a lot of Cocoa problems.
cug -- PharmaLine, Essen, GERMANY Software and Database Development
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
