Not clear on the issue(s) involved.  Is your web service consuming or publishing data?  Or both?  In an error scenario, what is it you want to have happen?

Anyway, here's my two cents:  Take a look at SQL, too.  I've used YAJL, IWS, and SQL for web services and my own experiences leads me to appreciate the great work Scott Klement did with YAJL but I came to realize that for publishing a web service it is really hard to beat the work of the folks that brought us the IWS wizard.  Simple, fast, and in my opinion, IWS handles errors quite robustly.   And, for consuming a web service, SQL is truly hard to beat.

The learning curves, for me, were painful but worth it.

On 1/24/2020 5:03 PM, Suren K wrote:
Hi All,

I am planning to introduce Web Services for my IBMi application. I need
some suggestion to choose which Web Services to go with.

This web services which i am planning will be mainly focused for REST Based
API Calls. Also i did a small POC in my application using Scott's YAJL tool
using DATA-INTO and DATA-GEN for Parsing JSON Document into Data Structure
and vice versa. So i am planning to use Scott's YAJL tool as well.

Initially i thought of using IWS, but i could see the below two drawbacks
with IWS
1) In Error Scenario the JSON body will not be sent back to Client
2) It Supports only 4 HTTP methods (GET, PUT, DELETE and POST) but as per
my application requirement i need to use PATCH method as well.
Do any one knows when IBM will fix the above two stuffs? If it is within 3
or 6 months then i am very happy to use IWS as Web Services.

The other options in my mind are
1) With Apache HTTP Server and using CGI method, call the RPG Program
2) Node.js

Any suggestions would be appreciated.

Regards,
Surender K

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.