Desktop Red Apps FAQs
FAQs
FAQ Categories:
Note: To find general Red Apps FAQs see here.
com.sabre.edge.cf.host.Communication Service
Question: When I use com.sabre.edge.cf.host.Communication from multiple threads I sometimes get HOST000 error. What is HOST000 error and how to avoid this problem?
EMU_COMMAND Service
com.sabre.edge.cf.host.Communication Service
Question: When I use com.sabre.edge.cf.host.Communication from multiple threads I sometimes get HOST000 error. What is HOST000 error and how to avoid this problem?
Answer: This error might occur when session is locked and with obtained LockId com.sabre.edge.cf.host.Communication service is used from multiple threads. In general it is not recommended to use multiple threads to communicate with Sabre Host as, due to nature of this communication, there is no possibility to match properly responses to commands sent from multiple threads. Also, in such scenario it is not possible to handle commands with multiple responses.
To communicate with Sabre Host either let com.sabre.edge.cf.host.Communication service handle locking and unlocking session or use only one thread to send commands.
Answers
EMU_COMMAND Service
Question: What does Sabre Red 360 do if multiple Red Apps register active listening for the same emulator command in EMU_COMMAND?
Answer: Sabre Red 360 displays a Conflict Detected dialog to an end-user with a selection list of the Red Apps that are trying to process the command prefix. An end-user selects the Red App that he or she wants to complete its processing.
Question: How does an end-user use this Conflict Detected dialog?
Answer: An end-user chooses the Red App that he or she wants Sabre Red 360 to process. The end-user has the option to save his or her selection. Whenever a conflict occurs again, Sabre Red 360 uses this selection without presenting the dialog to the user. If the end-user does not save the Red App that he or she selected, the dialog is presented again.
Each Red App in the list includes the Red App name, version, and vendor. When the user selects the Red App in the list, the dialog also displays a description of the app, the service name, version, event, and registered action code. The event, which is the command, will be processed according to how the Red App is designed to handle it.
Question: Can end-users view their selections or update their preferences?
Answer: End-users can view the list of services that they saved for processing. In Sabre Red 360, they choose Tools > Options > Red Apps Settings.
If they highlight a service in the list, the Red App name, version, and vendor are shown on the Settings page. The source of the description is the desc attribute of the RedApp element in redapp.xml.
End-users can remove an operation or service by highlighting it and clicking Remove.
If end-users remove an operation from the Settings page and a conflict occurs, Sabre Red 360 displays the Conflict Detected dialog again.
Question: What happens if a Red App that has been saved in the Red Apps Settings page is updated in Sabre Red 360, and a conflict among services occurs?
Answer: After the updated plug-in is installed on a user’s local workspace, the saved Red App is removed from the Red Apps Settings page. When a conflict occurs, Sabre Red 360 presents the Conflict Detected dialog again, and the user must choose the Red App or operation to complete its processing.
Question: As a Red App developer, how can I see and experiment with Red Apps that may result in a conflict?
Answer: Add the following Red App sample plug-ins together to your run configuration:
com.sabre.edge.example.cf.emu.bridge and com.sabre.edge.example.scribe
After you launch Sabre Red 360, type the 1 command in the emulator. Both of these samples listen for a command that begins with 1.