Abstract: A conference-enabled X application gets distributed to many different X servers, each of which may have different keyboard configurations. Each X server may have a unique range of key codes and a unique keysym to key code mapping. X protocol contains keyboard information in the form of key codes and a modifier bitmask that indicates which key code modifiers, such as the Shift key, are set along with the key code. In order for the conference-enabled X application to interpret the key codes in the protocol correctly, the X conference-enabler provides a technique to translate the key codes between the various X servers in the conference. The method it uses involves querying the keysym that a specific key code/modifier combination is interpreted as on one X server and then finding a valid key code/modifier combination on another X server that has the same keysym.

Abstract: A method of selecting which user has the input focus, and conditions by which a different user will get the input focus in the future. A user is said to have the `floor` if that user is enabled to become the input focus, or in other words, to provide input to the shared application. Zero or more users may have the floor at a particular time. (This is in contrast to a human conference or meeting where generally one person has the floor at a time). A method of selecting the set of users who have the floor is called a floor control policy. The floor control policy determines the set of participants who have the floor now, who will get the floor next, and how and when the floor assignments are made.