Proposed Implementation

New InSight CDI keywords that allow restriction of filter control. Control can be allowed/disallowed by device and by terminal number range/list. Also, control is restricted to listed applications. The following keywords are proposed:

AllowKeyboardFilter="" /* e.g AllowKeyboardFilter=”180-189, 280-289” */

AllowReceiptFilter=""

AllowScannerFilter=""

AllowAndisplayFilter=""

AllowAndisplay2Filter=""

AllowAndisplay3Filter=""

AllowVdisplayFilter=""

AllowVdisplay2Filter=""

AllowedFilterApplications="TestApp1"

Allow DeviceIOSendEvent to originate scanner, ANDISPLAY, VDISPLAY and printer data. The current DeviceIOSendEvent supports only keystrokes and manager key.

Allow DeviceIOSendEvent to modify and return filter control i/o requests. Filtered device i/o requests are likely to need additional information such as an i/o request sequence number.

Allow DeviceIOSendEvent to specify that an originated request is not to be handled independently of a of a pending i/o request. This ‘priority insert’ allows a filter client, for example, to display a message for 5 seconds, then complete a pending i/o request. Priority insert originate requests are never passed to other filter clients.

New QsaTerminalFilterControl MIB branch which contains the filter control and data watch tables and variables.

The filter client data watch tables. These device-specific tables are used to specify watch strings and resultant filter control mode settings. Data watch items are organized by client allowing multiple filter clients for the same device.

Ability to save the filter client data watch tables to disk as a configuration input file. This is needed to support the special case barcodes and keystrokes, which, even when the filter client is inactive, are never sent to the application.