Web Services for the Traditional Programmer, Part II

[Guest.Visitor]

It seems to me that most of the "monolithic RPG programs" that I have seen have been created for input to the database. "Web Services" seem to be geared towards output from the database. Why not query the database directly via some form of SQL and XMLHttpRequest, etc. (as I am sure many savy programmers do) and cut out the RPG middleman? Business logic is not Plasma Fusion Analysis - and most of the reports and output that I have produced in the last few years were simply database queries. "Back Office" and "Night processing" are horses of a different color though, and I doubt they will be superceded by .asp's, .net's, or java in any way, shape or form very soon. Just dump the RPG when you need web access.

[MCWebsite.Staff]

Web Services for the Traditional Programmer, Part II

0

[Guest.Visitor]

Web Services for the Traditional Programmer, Part II

The process that the author describes gives you the ability to leverage existing applicaiton code. While he uses a simple app for his example, you could just as easily be utilizing an existing "API" type program.