JSON is by far the better solution. That's probably why EGL supports both JSON and SOAP for communication between layers. But the idea of writing a 5250 program and using that to talk to the web is definitely very old technology. Heck, that's what my PSC/400 tool has been doing for ten years.

The right answer is to write programs that act as services. IBM i programmers need to learn how to write callable business objects, period. Then it doesn't matter what the front end is. To that end, anything that extends the 5250 interface is purely tactical, not strategic. Instead, by encapsulating your business logic in services, you can use whatever framework you want.

Obviously I prefer EGL :)

http://www.ibmsystemsmag.com/ibmi/open_egl/34329p1.aspx

Joe

And why use XML in a browser based solution ? this is yesterday technology
XML is fantastic to webservices, but slow in a browser where todays
dataformat
is JSON that goes directly into Javascript objects without any passing.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.