One of the biggest issues in warehouses across industries is productivity loss due to dropped wireless telnet sessions. The culprit in many cases is the architecture of traditional telnet solutions, which were designed over 40 years ago for use with wired, not wireless, environments. With an estimated 70% of wireless devices in the warehouse running mission-critical applications via telnet the scope of this issue is apparent. If approached correctly, a majority of these dropped sessions can be eliminated.
Traditionally, rf/wireless terminal emulation products and solutions have utilized software that resides on the wireless scanning device (client-side) and have provided an interface connecting to a generic telnet service on the host. The problem with this approach is that the environment within which the emulation software must operate is inherently more unstable than the application host and is prone to unpredictable and unplanned outages.
Telnet session interruptions (due to such factors as battery replacement, the user going out of wireless network range with a device, a device reset or reboot, etc.) are all part of the client device environment. AS such, these interruptions are outside of the client-resident terminal emulation software solution’s control. Therefore, deploying terminal emulation software on the client side of the wireless connection does not offer the opportunity to create a solution that would prevent the dropped (or abandoned) session condition.
This reality is one of the key drivers that have motivated today's software solution providers to adopt more server-based solution architectures that feature very thin client software functionality. This is done to lessen the impact of unexpected client-side events on the integrity of the overall connectivity solution.
Mobile device end users and help desk personnel have become accustomed to dealing with disrupted telnet sessions (and potentially lost data) on a daily basis.
If these persistent and costly disruptions could be eliminated, productivity could be increased significantly.
With StayLinked, all terminal emulation sessions remain on the host computer, with only a thin client installed on the remote wireless device. This thin client communicates with the host-resident StayLinked server to communicate keystrokes and scans to the emulation session and then to your application, and transmits only net changes to the emulation screen back to the wireless device. Network traffic is minimized, and all session data remains securely on the host, safe from intrusion or interruption.
Wireless workers and IT staff get relief from device lockups and connection issues. The end result: a better bottom line for your business.
Click below for a free trial of Staylinked