Re: what could have been - include HTML in the 5250 data stream

But that's the point. It's HTML and CSS and JS. It's not 5250 display file
protocol and fields. The technology was in place to enable applications
that used 5250 to use a different UI. Certainly the apps would have to have
been rewritten since most weren't already written in a modular manner that
separated the logic from the display. But changing an existing protocol
(5250) to one that already existed (HTML, et al.) seems not to be the best
use of money or time.


On Tue, Apr 9, 2013 at 9:18 AM, Steve Richter <stephenrichter@xxxxxxxxx>wrote:

Why should they have done that? There already was a technology in place.
The 5250 (and 3270) protocol was designed for one thing; reworking it to
solve a problem that didn't exist seems to be a waste of resources.

gosh, all the effort that has gone into reenabling 5250 apps over the
years, I think there was definitely a need to enhance 5250. Partly the
answer for why 5250 went nowhere is because of the interactive tax on the
system all those years past. But technically, I think there was plenty
that could have been done. The great progress of HTML and javascript atest
to that.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.