× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: No 5250-based applications
  • From: "Nathan M. Andelin" <nathanma@xxxxxxxxx>
  • Date: Thu, 26 Apr 2001 14:58:49 -0600

> From: "James W. Kilgore" <eMail@James-W-Kilgore.com>

> Nathan,

> You're not alone in the quest for a browser interface to replace 5250
> data streams.

> There have been threads about this issue in the past.  There have been a
> couple of arguement against it:

> 1) stopping the user from pressing the browser 'back' button.

Not sure what you mean?  I have never had a problem with a user clicking the
<back> button.

> 2) The amount of data that now must be pushed through
> the pipe.

That's what big pipes are for <smile>.  Actually, this is something the
developer should take into account.  The trick is to design a non-bloated
user interface.  GIF images are relatively small, and are cached by the
browser after the first download.  So they work well as a <Fn> key
replacements.  Another key is to use style sheets rather than in-line
styling.  The browser can cache a style sheet that is used across dozens of
pages.  Less HTML to download.

> 3) (related to above) The time it takes to format an HTML
> page and all the building/parsing that has to happen to
> exchange information.

The solution to this is a framework of generic reusable components.  It
really saves a lot of coding normally devoted to parsing input and building
output.  I use externally defined HTML templates, similar to externally
defined 5250 record formats.

With the help of a Web framework, code and maintenance are rather trivial.
Nevertheless, all Web applications require more CPU and memory.  For me,
that's the big difference between Web and 5250 applications.

> I'm kicking around the idea of taking the guts out of our
> interactive programs and have that workload performed
> by a batch program.  The interactive workload becomes
> trivial and therefore not as likely to trigger the governor.

Hmmm, design an application around the CFINT governor?  Sounds pretty
desperate.  In my opinion, 5250 applications and the hardware required to
run them are still a bargain, even with the governor.  Just divide the
hardware cost by the number of active users, then compare it to the cost of
supporting an equivalent number of Visual Basic users.

Nathan.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.