Re: More efficient web service choice
Re: More efficient web service choice
- Subject: Re: More efficient web service choice
- From: David den Boer <email@hidden>
- Date: Thu, 19 Jun 2008 00:21:06 -0700
Same with us. A properly architected API solves all of these problems
and then some. You have to architect it using only standard java data
types -- dont use EOF/NS or collections -- you screw yourself when
working with non-java clients.
What I like best about SOAP -- its dead simple to develop for when you
use WO, and rock-solid. We even have stateful webservices using
database backed sessions -- all of our API's (except authenticate)
take a SessionInfo object (our own object type made of simple objects
including a wosid), and we restore the session from the database using
that object.
If you're developing rock-solid enterprise class API's to be used by
clients across a wide spectrum of tools/operating systems, I think you
can do no wrong using SOAP. If you like PHP or RoR, go the other way :-)
On Jun 18, 2008, at 6:23 PM, Lachlan Deck wrote:
On 19/06/2008, at 1:52 AM, Guido Neitzer wrote:
On 18.06.2008, at 00:03, David den Boer wrote:
We use SOAP webservices on many of our applications, some of which
receive several hundred thousand transactions daily without any
issues. I find the ease of using SOAP over other options so much
better, especially when using WO (which is also quite a bit faster
than using JBOSS or Tomcat for webservices BTW).
SOAP is just a bitch if you don't have only WO apps connecting to
each other or if you have several versions of Axis (from different
clients) or if WO somehow decides not to create a completely
correct WSDL (happened a couple of times in the past).
So, SOAP *might* be an option, personally I like the more less
complex protocols better. SOAP is just plain not simple and easy
and straightforward.
I haven't had that experience (not to invalidate yours). Our non-wo
apps happily communicate with our WO app (even using differing Axis
versions).
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden