public interface DesktopUpdateCapable extends Capability
This interface declares client capability to receive updates of the
remote desktop image. There's usually a mechanism allowing the server to notify
the client of any desktop change and clients are able maintain an up to date
copy of the server desktop image. There are no methods because clients
implementing this interface declare that they may fire events of desktop
update through the RemoteDesktopServerListener
listener interface. Typical examples of active protocols are RDP and RFB.
The other sort of clients is sometimes called passive. There's usually no mechanism to receive asynchonnous events about desktop updates. Such clients typically refresh their local copy of desktop image at scheduled intervals or according to a plan or strategy. The image they maintain may or may not be up to date. Typical examples of such behavior are local desktop drivers, for example the Java native client.
This interface has impact on behavior of the Waitfor update
scripting command. If the client implements it, the command attaches to
the screen update message flow from the server and waits for the given
rectangle (or scope) to refresh. If the method returns false, the command
rather actively refreshes the image at scheduled intervals and attempts
to detect differences between the original and refreshed image. This may
lead to late desktop change detection. For this reason clients which
do not implement this interface are not recommended for load or performance
testing where it is necessary to measure exact time from a user action to
the corresponding desktop update (for example an application start).
T-Plan Robot Enterprise, (C) 2009-2022 T-Plan Limited. All rights reserved.
| Modifier and Type | Method and Description |
|---|---|
boolean |
isKeyTransferSupported()
Allows to switch dynamically support of desktop updates.
|