|
On Dec 15, 2015, at 6:08 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
On 12/15/2015 4:47 PM, Nathan Andelin wrote:
I've always considered HATS to be a "stepping stone technology" and not a
destination technology.
Call it "stepping-stone", "interim", "stop-gap", "make-shift",
"provisional", or whatever. Each of those terms is being overly generous to
every screen-scraping product out there. Transforming 5250 streams into
browser DOM objects makes the UI worse - not better, IMHO. You're adding
something like 30-100 times more CPU overhead, something like 20 times more
bandwidth, and reducing the productivity of end-users.
I'm not OP and I don't know the context of the request, but I can
sympathise. Imagine getting a decree from the corner office that the
company Shall Be Browser Based in 6 months. How would I do that, having
never once deployed a mission critical app to the web? I can argue with
the new CIO all I want, but he's new, he's making his mark in the world
and I'm a dinosaur in his eyes.
I might be making that a little too personal :-/
ps I utterly agree that a webified 5250 application is hideous compared
to a web app that was conceived, designed, implemented, and deployed as
a web app from the start.
--
--buck
Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
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.