IBM i 5250 protocol terminal emulation and integration on the Web with Flynet Viewer or Screensurfer offers a number of advantages.
The Flynet approach utilizes the latest AJAX DHTML techniques to ensure that user keystrokes are identical to those found in traditional desktop emulators (including keyboard buffering) and that any host writes to the screen are immediately reflected in the web browser. 5250 protocol integration in a Screensurfer environment uses a different technique to ensure the same thing. True 5250 protocol -to-browser Gateways such as Flynet and Screensurfer can both exploit and optimize CSS-based customization of the IBM Mainframe 5250 protocol attributes.
A standard 5250 protocol terminal emulator, on the other hand is just like what you have today!. Why bother delivering 5250 protocol Internet applications unless you are going to improve them?
We call traditional 5250 protocol emulators ported to execute in the Web environment the "emulator-in-a-box" solution. That is because while users initiate emulation from a "real" HTML web page, the result is typically a separate window that pops-up and becomes the 5250 protocol terminal emulator. This window is typically a Java Applet or an ActiveX control, and offers little integration with other HTML page objects, meaning little integration with your pages!
Integration with a mainframe 5250 protocol application is also possible with both tools, with Flynet Viewer providing integration with .NET and Microsoft tools and Screensurfer providing a standalone ability to integrate with the 5250 protocol.
Please select from the menus or the subject icons to the right to learn more...