Superb green screen; painless printers

Bulletproof greenscreen technology creates virtual copper wire between you and your Internet based server.

The problem for programmers

If you have tried to program using Telnet or SSH over the Internet, you have almost certainly experienced the problem of having your connection broken. Depending upon many local factors, you may find it being broken after as little as 5 to 10 minutes. When this happens, your program, unless saved, is lost and you have to reconstruct it.

The problem of data entry

Green screen data entry is not about to die, for two reasons. First of all, a well trained "heads down" data entry user is often 10 times as productive in a green screen environment as they can possibly be in either a web or GUI environment. (Web and GUI have the greatest value in organizations that have the highest employee turnover, or in for casual users of applications.) Second, there is just an immense investment in green screen applications, and green screen applications are often a lot less expensive to develop.

Failure of green-screen in an Internet environment is more problematic than Web, in part because the operators are less skilled at reconnecting, in part because valuable data may not only be lost but be un-reconstructable, and in part because the operator may have to go through several levels or formatted screens just to get back to the right point.

The problem of network printers

Anyone who has attempted to manage network printers over the Internet often feels as if they spend half their life repairing or reattaching broken network connections and recovering print jobs. Bulletproof greensceen's virtual copper technology ends this problem. Printers just stay connected rather than needing recovery work.

How our bulletproof
greenscreen technology
fixes these problems

Bulletproof greenscreen ends the lost connection problem by establishing a local connection between the application and itself. Thus, the connection is held open and is usable even if specific Internet connectivity is lost, preventing the loss of data or programs.

Our bulletproof process then proxies the results of the local connection over the Internet, with ability to auto-switch between at least two different backbones and buffering if one of the two dies in the middle of a transmission. Determination of the best circuit, at present, is done by sending a ping package down the line every 5 seconds to determine relative line quality of the different circuits. This not only fixes broken connections but automatically picks the "best" line, even adjusting for packet loss. As a result, at distances of even 2 or 3 thousand miles from the data center, our bulletproof connection often has no visually noticeable echo delay.

At the client end, bulletproof again proxies the connection to the local device and engages in protocol conversion to a terminal emulator, local shared printer, or serial-port device.

Because our bulletproof process is a client originated connection, it works from virtually anywhere, while it's web configuration reduces connection setup times to just a few minutes. As importantly, the server-side connection is painless, because all devices are piped as serial devices. All you need to do is point a greenscreen or printer session at a bulletproof greenscreen-enabled tty and it will just "work."

Triple-DES encrypted

Easy-Connect has built in triple-DES encryption, assuring that your data moves over the Internet safely.

The virtual copper reliability
of our bulletproof method

Most people who try to connect people over the Internet spend their lives reconnecting things, or providing assistance on reconnection because SSH, Telnet and SMB connections will fail in a few minutes or hours, depending upon local conditions. Our bulletproof method just works. We can go for months and even years at a time without hearing from customers about connectivity problems. And when we do hear from them, 9 times out of 10 the problem boils down to one of two things: (a) either loss of their own local connectivity (they forgot to check and see if they could get to cnn.com or weather.com before they called us for support, and with our help discovered that their local ISP was down), or (b) their Windows PC was running too long, and accumulated some corruption in their stacks.