Re: SOAP vs. REST -- WEB400

Subject: Re: SOAP vs. REST
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Wed, 10 Jul 2019 15:51:47 -0500
List-archive: <https://archive.midrange.com/web400/>
List-help: <mailto:web400-request@lists.midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.lists.midrange.com>
List-post: <mailto:web400@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@lists.midrange.com?subject=unsubscribe>

I admit I had a ton of trouble. In every instance it was because I was over-thinking. The documentation was accurate but overwhelming. That is part of my case FOR IWS. It needs a more intuitive interview, but lest we forget... Programmers like me are the audience for IWS. The folks already whizzes with PHP, Python, et al are not the target for IWS.

I have used Scott's HTTPAPI and like it but IWS does what HTTPAPI does and does it wizardly.

On 7/10/2019 3:17 PM, Jon Paris wrote:

On the other hand, even using the IWS wizard requires that you understand a lot of rather arcane terminology which the manuals describe in "Unixese". And I_know_ you had a lot of problems with that because I watched your posts here on the topic.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SOAP vs. REST , Jon Paris

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.