Timeline for Convincing a Client to Offer a RESTful Web Service instead of a SOAP Service?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2011 at 19:22 | comment | added | MikeSchinkel | Here's the issue. Unless the cost/benefit ratio is something I can do and reuse, this issue is often coming up at the front-end before payment when the client has said they want to use me because of my WordPress plugin expertise and specialization but then they tell me they are building a SOAP web service for me to call and they've yet to commit to pay me anything. But thanks, I think by discussing this issue I'm getting what I need. | |
| Apr 16, 2011 at 11:43 | comment | added | Joel Etherton | @MikeSchinkel: Not having done wordpress plug-ins I can't really provide any insight in that direction. If these points you raise are this impactful then it shouldn't be difficult to generate a cost/impact analysis for the management team. If you can clearly demonstrate that SOAP will be costing them time/money you shouldn't have any difficulty changing their minds on it. If they still don't then your choice might be made for you. | |
| Apr 16, 2011 at 5:38 | comment | added | MikeSchinkel | Also, if I'm right about the issues I might have with supporting SOAP, I'll be doing the "customer" a huge favor but guiding them to REST. | |
| Apr 16, 2011 at 5:37 | comment | added | MikeSchinkel | There may be truth to "comfort zone" but regarding the supportability of SOAP within a widely distributed WordPress plugin, not about any lack of desire to learn. Frankly I'm one that always learns new things about WordPress (here's proof) and part of me wants to learn PHP+SOAP, but I don't want to make a mistake and end up with tens if not hundreds of support issues because of using SOAP where I shouldn't. And in these cases, there are not yet customers, they are prospects. No bills paid yet. :) | |
| Apr 16, 2011 at 5:21 | comment | added | MikeSchinkel | I will move on if I can't find a way to keep the WordPress plugins from having to access SOAP. But if I can get their management to understand why SOAP is problematic for this use case without alienating their programmers then I would like to. I'm not casting blame so much as describing the outcome. If there is any blame it is Microsoft's but I recognize Microsoft thinks it's in their best interest and they are far too profitable for me to argue that it is not. I'm not blaming the .NET programmers; I once programmed the Microsite-stack and I knew little about HTTP then. | |
| Apr 15, 2011 at 13:58 | history | edited | Joel Etherton | CC BY-SA 3.0 | grammar edit |
| Apr 15, 2011 at 13:07 | history | answered | Joel Etherton | CC BY-SA 3.0 |