Re: Weird IWS Bug (?)

Booth:

While I’m just getting into it, YALJ and JSON just do not look to be that
daunting given the work Scott and partner (don’t remember the fellow’s name
off hand) did to port it to IBM i. Particularly with the updates IBM put
into RPG recently.

Even the http api calls don’t look too bad. Of course I still have to
write the first one and debug it but I think I’ve got most of the shell
done and I just need to add the business logic.

We shall see.

On Thu, Jul 18, 2019 at 1:30 PM Booth Martin <booth@xxxxxxxxxxxx> wrote:

The issue, to my mind, is about alternatives. The RPG shops already
using YAJL or whatever are happy and have no real reason to change.

However, the many good, long-time RPG shops that find that they must
move into the XML/JSON world can get there with existing people a lot
quicker with IWS. IWS provides existing teams with an on-ramp that is
gradual, productive, and effective from about Day 4 (with a decent
tutorial/teacher).


On 7/18/2019 1:17 PM, Jim Oberholtzer wrote:

My thought was the client and server program both “speak” JSON between

them

and IWS manages the server instance etc. That’s where Scott Klement’s

YAJL

and HTTPapi come into play.

Am I wrong? I can see where IWS could be avoided.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.

--

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects