c******n
发帖数: 4965 | 1 I know it's a dead horse.....
but I think it's too much hype and ultimately the issue is simply
serialization/deserialization of messages, like the way Thrift treats
it.
ultimately programmers just need to treat the service as an interface
and call that using the language that expresses the service. SOAP/REST
is simply an encoding of the rest ( XML envolope vs encoding of the URL
), developers should not care about such encodings, instead they should
simply care about the service language.
at | s******e
发帖数: 493 | 2 one thing that is always poped up in the debate of soap vs rest is the
simplicity of the protocol.
many think that rest protocol is much simpler and easier to use than soap.
But this really depends on your background and your taste.
xml seems to be more verbose than json considering the download and upload
size. this is also an important factor you have to weigh out if you have a
global deployment, especially for users with a limited bandwidth, high
network latency, and/ or slow network speed. | t*******e
发帖数: 684 | 3 Use SOAP/WSDL/XML for B2B, heavy-weight, and transactional communications.
REST/WADL/JSON is more efficient for high-frequent, client/server
communications, such as Ajax. In many places, such as CMS/DMS, both flavors
of web services are supported. |
|
