Re: More efficient web service choice
Re: More efficient web service choice
- Subject: Re: More efficient web service choice
- From: Paul Lynch <email@hidden>
- Date: Wed, 18 Jun 2008 19:33:00 +0100
On 18 Jun 2008, at 16:52, 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.
That's my experience as well.
A SOAP interface where the other end doesn't really quite understand
what they are doing is a recipe for torture. Poor SOAP APIs are
crippling, and forgetting to distribute the wsdl can create an amazing
amount of downtime; not to mention insisting on sending out the wsdl
rather than putting it on a url.
It can also be rather tricky to persuade WO to talk to alien (read "M!@
£$%") SOAP servers/clients.
I'd rather be using REST. Or anything else, for that matter.
Paul
_______________________________________________
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