Friday, April 15, 2016

Moving from Telnet to Web the Truth Revealed

Moving from a telnet based interface to a GUI like a web browser is always a tough decision for most U2 shops. However, most vendors sometimes "Lie by Omission". Let’s take apart the decision and talk about what the other vendors say or don’t say about this processes.
Web browser interfaces is slower than telnet. When your people can open several browser tabs to see information that would take them multiple enter keys to find in telnet that argument can be rendered moot.  The other issue is data entry speed is better in telnet. If you have written the user interface (UI) in JavaScript, there is no latency speed issue to go to the server because most of the data entry correction and verification is taking place on your web browser. For the most part, your vendor can, with a lot of work, negate this issue.
Converting from telnet to web is quick. Most if not all of your logic in your programs is based on receiving information from each telnet prompt. No web interface works like that.  At U2logic, we try to send either an entire multi-valued line of information at once or the full screen to do the database integrity testing at the database level. The logic of your programs for a different UI’s means removing a lot of code and restructuring the flow to be more batch mode instead of interactive mode which will take quite a lot of time to get it right.
Web programs will save you money in the long run.  This one is very true. Once you have made the jump to a web browser your business can grow without the need to hire more people because of productivity gains.  Additionally, when turnover happens which is expensive, you training time is significantly reduced for those new employees.

No comments:

Post a Comment