Honeywell HX3, Руководство пользователя, Страница: 109 / 230

6 - 17
Notifications disabled, HX3 is not Write Capable
1. The OPP client initiates a connection to the HX3 by selecting a file to push to the HX3.
2. The file is rejected silently (no notification to the HX3 user).
HX3 Pushes File to Remote Device
This section assumes that a device supporting OPP is paired with the HX3.
The HX3 (OPP client) initiates a connection to the remote device (OPP server) by selecting a file to push to the remote
device. The HX3 sends the file and disconnects. The remote device may prompt the user (of that remote device) to accept
the incoming request depending on the security settings of the remote device. The prompt may be displayed more than
once, or it may not be displayed at all.
Notifications enabled
The file is pushed to the remote device and the user of the HX3 is notified of the completion of the push.
Notifications disabled
The file is pushed to the remote device and the user of the HX3 is not notified of the completion of the push.
LXEZ Pairing and External Application
Because only one application can use the OPP service at a time, external applications that wish to use OPP should disable
LXEZ Pairing OPP before using the OPP service and restore LXEZ Pairing OPP upon completion using available API calls (see
the
CE API Programming Guide for details). These API calls are the equivalent of checking or unchecking the Disable LXEZ
Pairing OPP check box.
• If Disable LXEZ Pairing OPP is not checked, checking it causes LXEZ Pairing OPP to be disabled and the send and receive
functionality is disabled.
• If Disable LXEZ Pairing OPP is checked, and no application has registered a callback, un-checking LXEZ Pairing OPP
enables OPP functionality in LXEZ Pairing, and the send and receive functionality is enabled.
• If Disable LXEZ Pairing OPP is checked, and another application has registered a callback, un-checking Disable LXEZ Pairing
OPP issues a dialog box which says “Another application is using OPP. Do you wish to force their disconnection? Doing so
will force the other application to be unregistered.” The application that has been forcibly unregistered receives a
FORCED_UNREGISTER_RECEIVED event.