• You are losing out on amazing benefits because you are not a member. Join for free. Register now.
  • Big Two-Day Giveaway - Win an Amazon Kindle, a Mystery Gadget and Branded Gear. Enter Here.
  • Test your broadband speed and win prizes worth R5,000. Enter here.

Sending data to a webservice

Spacerat

Senior Member
Joined
Jul 29, 2015
Messages
720
#43
Good Lord how I hate SOAP. The worst was way back I had to integrate to a service using SOAP. They did not have XSD nor WDSL. Only one sampke piece of SOAP request response. I had to jump though many hoops at the time to get it parsed. But that was not likely SOAP's fault per se.

Nowadays when clients need to integrate to my services and they use C#, at least I give them the assemble I use that contains all the DTOs. At least when they JSON serialize/deserialize they use the same classes as I do. Or use Swagger if using REST
 

Hamster

Resident Rodent
Joined
Aug 22, 2006
Messages
29,282
#44
Cute, but your shitty queries take way more processing than the SOAP message.
Well I've never heard of a SOAP fanboy before but here we are. Comparing SOAP processing to SQL processing is stupid.

And don't you judge my SQL queries until you've seen them guy.
 

kolaval

Expert Member
Joined
May 13, 2011
Messages
2,275
#45
Hardly a fanboy, just indifferent. When a customer(and I mean big companies) says "we need data, here's our wsdl" you don't respond with "herpes". It's irrelavant.

SOAP processing, SQL processing it's all CPU cycles at the end of the day.
And I have had to fix enough SELECT * to know where the server bottlenecks are.

Just
like
yours

guy.

:p
 

_kabal_

Expert Member
Joined
Oct 24, 2005
Messages
2,500
#46
Good Lord how I hate SOAP. The worst was way back I had to integrate to a service using SOAP. They did not have XSD nor WDSL. Only one sampke piece of SOAP request response. I had to jump though many hoops at the time to get it parsed. But that was not likely SOAP's fault per se.

Nowadays when clients need to integrate to my services and they use C#, at least I give them the assemble I use that contains all the DTOs. At least when they JSON serialize/deserialize they use the same classes as I do. Or use Swagger if using REST
My favourite SOAP services are the one that take a CDATA'd XML payload in the body.

The WSDL/XSD basically generates

XML:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Header/>
   <SOAP-ENV:Body>
      <Data>?</Data>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
 

semaphore

Executive Member
Joined
Nov 13, 2007
Messages
9,960
#49
Hardly a fanboy, just indifferent. When a customer(and I mean big companies) says "we need data, here's our wsdl" you don't respond with "herpes". It's irrelavant.

SOAP processing, SQL processing it's all CPU cycles at the end of the day.
And I have had to fix enough SELECT * to know where the server bottlenecks are.

Just
like
yours

guy.

:p
Yes, but there are more efficient data transport formats out there now. If you are developing a new service and still using SOAP you need to have a frontal lobotomy. For legacy systems entrenched with this I can understand.

SOAP process vs SQL processing are not even remotely the same thing, one is a transport format the other is a language designed for querying databases. Your comment regarding CPU cycles is entirely moot.
 

Spacerat

Senior Member
Joined
Jul 29, 2015
Messages
720
#50
My favourite SOAP services are the one that take a CDATA'd XML payload in the body.

The WSDL/XSD basically generates

XML:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Header/>
   <SOAP-ENV:Body>
      <Data>?</Data>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I very much agree: KISS
 

[)roi(]

Executive Member
Joined
Apr 15, 2005
Messages
5,636
#51
SOAP while awful is certainly not the worst of what's out there; and the fact that its prevalent in certain spaces is more a subject of timing rather than any specific good attribute.
 

kolaval

Expert Member
Joined
May 13, 2011
Messages
2,275
#58
I gather from the responses here that many have been burned by k@k SOAP.
Hence the hate.

But if you get a proper wsdl, coding against it is a piece of cake.
 

[)roi(]

Executive Member
Joined
Apr 15, 2005
Messages
5,636
#59
I gather from the responses here that many have been burned by k@k SOAP.
Hence the hate.

But if you get a proper wsdl, coding against it is a piece of cake.
It's got nothing to do with being burned by anything.
SOAP simply is an bad solution to every problem; it's neither light weight or fast or flexible or simple or...
 
Top