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

Subject: Re: what could have been - include HTML in the 5250 data stream
From: Steve Richter <stephenrichter@xxxxxxxxx>
Date: Tue, 9 Apr 2013 09:18:25 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

Follow-Ups:

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

This mailing list archive is Copyright 1997-2026 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.