Timeline for Convincing a Client to Offer a RESTful Web Service instead of a SOAP Service?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2016 at 0:51 | comment | added | Jerry Jeremiah | I have almost never seen a SOAP message that only took an ID and some authentication token - Some of the requests I have had to make are kilobytes long and return megabytes of response. | |
| Apr 18, 2011 at 9:35 | comment | added | MikeSchinkel | @Berin Loritsch - Thanks again for your help. In many of the cases the clients are running IIS servers so I'm thinking asking them to run a Linux/Apache server just for this is probably a bigger ask them asking them to just write a REST service in addition to the SOAP service. But again, you've been helpful and I appreciate it. | |
| Apr 16, 2011 at 20:47 | comment | added | Berin Loritsch | All I'm saying is that you have options. The correct answer depends on a variety of factors. For example, there only needs to be one wrapper deployed. The other users would merely connect with that one wrapper. You know the details of your integration better than I do. As I mentioned, the wrapper doesn't have to be hosted on IIS. There are other SOAP stacks that are compatible with the Linux/Apache stack. If your clients are not willing to support the wrapper, you need to deploy it somewhere you control. | |
| Apr 16, 2011 at 19:43 | comment | added | MikeSchinkel | @Berin Loritsch - This is a WordPress plugin, so it will be distributed to users of WordPress who could be hosting anywhere and almost always on Linux servers. But the wrapper should be able to run on the IIS machine, right? The most recent client has their own applications and I'd be writing a plugin for them to distribute. The wrapper would definitely need to be hosted on the client's servers who are also hosting the SOAP otherwise the would be no benefit to a wrapper. | |
| Apr 16, 2011 at 11:58 | comment | added | Berin Loritsch | It's an independent layer, so you have some flexibility on where you want to install it. Assuming you are hosting your Wordpress application on IIS, you can install it right next to your Wordpress application on your server. You can have a separate machine host it, or you can have the client host it next to their web services. You will have the most luck if it is part of your own application solution. Even if you are not using IIS to host Wordpress, you can implement the wrapper in a language supported by the web server you use. | |
| Apr 16, 2011 at 6:12 | vote | accept | MikeSchinkel | ||
| Apr 16, 2011 at 5:16 | comment | added | MikeSchinkel | ...Your wrapper ideas leaves me with two questions: 1.) Is this something that can easily be run side-by-side on their server or will it need more infrastructure on another service? Can this be offered up as a self-contained thing we give them and say "Here, install this?" 2.) Are you available on a freelance consulting basis to build this and/or future SOAP wrappers? (I'm asking seriously.) | |
| Apr 16, 2011 at 5:13 | comment | added | MikeSchinkel | @Berin Loritsch - Thanks for the answer. I do not know the (current) Microsoft stack, hence the reason I asked the question. Is SOAP based on WCF? Your point about PHP and SOAP is bang on and why this is an issue. I wouldn't be asking this if I were developing for them in C#. And if I'm using PHP:SOAP, I asked this question in the rare case I do decide to try and implement against a SOAP service: wordpress.stackexchange.com/questions/14804/… That said, your "wrapper" idea sounds excellent, but... | |
| Apr 16, 2011 at 5:08 | comment | added | MikeSchinkel | @Jacek Prucia - "Problems with PHP, not SOAP/WS itself" - Exactly. That was (should have been) implied by my first sentence which said I was writing plugins for WordPress. .NET to .NET SOAP works brilliantly, but that's not what I'm doing. | |
| Apr 15, 2011 at 15:02 | comment | added | Jacek Prucia | +1 I would also add, that all the problems Mike pointed out are really problems with PHP, not SOAP/WS itself. | |
| Apr 15, 2011 at 13:07 | history | answered | Berin Loritsch | CC BY-SA 3.0 |