RE: XML and RPG-CGI, is XML needed. was -> HolyWar . . ..

> From: Bartell, Aaron L. (TC)
> 
> Ok, now we have something worth talking about.  I will give some
history
> to that statement. . .

Hee hee!  See, I knew we could get past that little "testosterone
moment" <chuckle>.


> In my experiences, passing values to a CGI program (RPG in this case)

See, my original point was that I wouldn't use an RPG program here.  I
would use a servlet to intercept the external request, and then call the
RPG program.  By doing this, I can move the servlet off of the iSeries
box (because the Java toolbox makes it very easy to call a program on a
remote machine), thereby "decoupling" the web server from the business
logic.

See what I mean?


> with a
> key value pair (Name=Aaron&State=MN for example) proved to be less
than
> adequate when you want to get a whole heap full of info into the
RPG-CGI
> program, and then what do you respond with, more key value pairs, XML?

Here I agree!  I like XML as a platform- and protocol-neutral
communications medium, for situations where you have the bandwidth.  As
I'm sure you agree, there can be a lot of additional overhead with an
XML file, but as a sort of "buffer zone" between differing platforms
(especially when you're trying to be as open as possible), it's not bad.


Notice, though, that while we agree in one place (XML) and disagree in
another (servlet vs. RPG-CGI), neither of us is even mentioning web
services.  That's because they're really not relevant to the business
question.

Web services come into play when you're talking about finding a service
provider.  If you don't know where that provider is, then web services
are a sort of directory.  But short of that, I don't find them to add
anything to the basic concept of sending an XML file to a program and
waiting for one in response.

And frankly, I have a little trouble with the idea that I am going to
want my mission critical systems to go to some public directory to
determine where to send my sensitive information.  I think web services
may indeed be important for querying data, but probably less so for
transaction processing.

But this area is definitely still up for grabs, and I'm just as likely
to be right as wrong; only time will tell.

Joe