Re: RPG easier/harder to use than other languages?

"The answer is to switch from an ODBC interface to a web-services interface,
which has no problem with hierarchically-structured data exchange (XML or
JSON). ODBC is also too hard to secure."

"hierarchically-structured" is correct. Exchange data as XML or JSON or
just plain text strings.

Business logic should reside on the IBM i. Putting business logic in GUI
screens is nuts.

Your "Returning to the idea of deploying web services" are you saying they
are bad idea or a good idea?

You have the same problem with web services. You get the web service
request to the server. Now what do you do with it? How do you invoke the
business logic?


On Fri, Jul 7, 2017 at 10:43 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

The problem with stored procedures is that they have parameters and
parameters are inflexible. You can use SQL to return result sets but what
happens when you try to send large amount of data or complex data?

The answer is to switch from an ODBC interface to a web-services interface,
which has no problem with hierarchically-structured data exchange (XML or
JSON). ODBC is also too hard to secure.

Notwithstanding the foregoing, the use of stored procedures has provided a
means of retaining business logic on database servers, which is where
business logic belongs. The migration of business logic off database
servers has been a huge travesty, and a blot on the IT industry as a whole.

The idea of moving business logic off database servers dovetails with the
problems that people have expressed regarding OO languages. OO has a place,
but the use of OO for business objects was a bad use case generally, and
its overuse has become a quagmire in many organizations.

Returning to the idea of deploying web-services as an alternative to stored
procedures, the impact on mainstream language environments that run on
servers (i.e. aspx.Net, PHP, Python, Ruby, Java) would be huge. There's
essentially no need for middle-ware language environments to be involved at
all. They just add latency, bottlenecks, potential failure points,
potential security risks. They would be utterly unjustifiable.

On the client side, browsers would likely produce and consume JSON. On the
IBM i side, RPG programs would likely produce and consume JSON.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD