I know someone will respond negatively to this idea - I do think it
might be useful to look at the integrated web services - here's the link -
I don't remember if it sets up REST yet - the site says SOAP 1.2.
This is a way to "...externalize ILE business logic as a service."
On 1/20/2014 11:42 AM, Koester, Michael wrote:
Given that this would not be for "public consumption" (i.e., only targeted at the web site developed for the business) would that be a problem? The web developer and I would agree on the spec, and it would only change for a mutually agreed upon design change.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, January 20, 2014 12:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: Web-to-i Communications questions
On 1/20/14 9:15 AM, Koester, Michael wrote:
Thanks Dan. I like the SOAP web service idea. I've done projects
Eeewww. I've had to consume SOAP; it tasted terrible, and gave me a
where I've consumed web services, but have not yet coded any that
provide. Seems like a fit, though. I'll check into that.
REST is much less strenuous than SOAP. At least in my experience, the
nastiest RESTful web services (e.g., Google Calendar) are still easier
to deal with than the friendliest SOAP ones.