Barcoding - Wireless Terminal Emulation
Stay-Linked utilizes the unique and proprietary Client2Host™
architecture, in which thin-client software is installed on
a remote device and used to connect to a Stay-Linked Server
on a host computer, where the Server creates a host-resident
Telnet or SSH session for the device.
All of the settings used in this architecture are centrally
configured via the Stay-Linked Administrator, a powerful centralized
GUI-based console which can be installed on any network-connected
Within this true thin-client architecture, keystrokes and
scans are transmitted from the client on the remote device
to the host-based session, where they are processed by the
end-user application, and the resulting terminal emulation
screen changes are transmitted back to the client on the remote
device and displayed.
reside on a host computer, not on a vulnerable wireless device
With legacy device-side terminal emulation (often given away
for free), terminal sessions reside on the wireless remote
device. Terminal sessions can be anywhere the remote device
goes. Behind a pallet. Under a forklift. In the break room.
And if the device is offline, the help desk can't help because
the session isn't visible. It's just MIA.
With Stay-Linked, terminal sessions reside on the host computer.
Safe and secure. Only the Stay-Linked thin-client device software
resides on the remote device, where it's used to send keystrokes
and scans to the host-resident session. Simply. Logically.
So even if the device is offline, the help desk can monitor,
take control, share, transfer or partner with the host-resident
session via the GUI-based Stay-Linked Administrator console.
emulation solution—not cobbled together
Real RF Solutions should be designed and built from the ground
up—not cobbled-together from hastily-created parts in an attempt
to mimic features introduced by Stay-Linked. Even numerous
add-ons and patches to free bundled legacy emulators don't
provide the reliability and functionality flawlessly provided
Others have tried to keep pace…
Before Stay-Linked was introduced in 2003, session persistence
and session management features--such as monitor, remote control,
share, and transfer—were not available. Since those features
were introduced by Stay-Linked, the 90's-era emulators have
added bits and pieces to try to match the Stay-Linked solution.
Proxy servers and gateways have been added, and device remote-control
is being touted as session remote control. These cobbled-together
offerings cause problems for resellers and customers alike,
and they just don't work as well as Stay-Linked in today's
Cobbled-together components drive up costs and introduce complexity—not
what you want from a terminal emulation solution.
Telnet remains on
the host—using port filtering, no telnet is broadcast
over the wireless network
Also provides SSHv2
(Port restrictions and Static NAT Configuration for Servers.
NAT friendly connections for Clients)
end-to-end, application layer encryption technology
(Dynamic-Symmetric 64-bit key, Stream-Cipher Symmetric