tag:blogger.com,1999:blog-551136829267421578.post3899570273662578958..comments2024-02-22T00:49:32.974-08:00Comments on Technology Solutions: REST vs SOAP Web ServicesAnhttp://www.blogger.com/profile/16257268735968644764noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-551136829267421578.post-10963241768632138952011-05-03T08:56:00.280-07:002011-05-03T08:56:00.280-07:00I should clarify, I've never had to deal with ...I should clarify, I've never had to deal with a SOAP wrapper in code. Register the wsdl and voila, you're done. If you're using notepad to write code, I guess this could be an issue.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-551136829267421578.post-34524321172749727772011-05-03T08:53:14.179-07:002011-05-03T08:53:14.179-07:00REST is just XML. Ummm, so is SOAP. The SOAP wra...REST is just XML. Ummm, so is SOAP. The SOAP wrapper is XML. "Relative" ease of use is right on the money. With the right tools, in my opinion, SOAP is much easier to implement than REST and shields the developer from any of the "plumbing" required to make method calls. True, REST is bare metal http, but whether it's objective to say that's better is a matter of opinion. The REST services I've tried to connect to tend to be lacking in standards in my opinion and seem to be pretty "loosey goosey" in their implementation. However, that's my experience dealing with custom integration. I'm sure commercial vendors are much better at adhering to some accepted standards.Anonymousnoreply@blogger.com