Bug 31442 - Adapt computerroom/* commands to be stateless
Adapt computerroom/* commands to be stateless
Status: REOPENED
Product: UCS@school
Classification: Unclassified
Component: UMC - Computer room
UCS@school 5.0
Other Linux
: P3 normal with 2 votes (vote)
: UCS@school 3.x
Assigned To: UCS@school maintainers
:
: 30074 41317 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-24 10:26 CEST by Alexander Kläser
Modified: 2023-06-23 14:19 CEST (History)
6 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Cleanup
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-05-24 10:26:07 CEST
Currently, the command "acquire" initiates a computer room for the running session. Consequent calls to the command "query" or "update" (without parameters) refer to the initially initiated room.

As this results in different problems (no to rooms can be opened simultaneously), it would be better to design the commands to be stateless, i.e., with an additional parameter indicating the room, the command "acquire" could then be removed.

In addition to this, the command "update" only returns changes in the room since the last call. This, as well, results in problems if the same room is opened twice (only one module will receive a change). To render this mechanism stateless, the query method could be used instead (it returns the current known status of all computers), and changes could be detected via JavaScript.
Comment 1 Florian Best univentionstaff 2013-05-27 09:24:20 CEST
*** Bug 30074 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2016-05-23 09:38:53 CEST
*** Bug 41317 has been marked as a duplicate of this bug. ***
Comment 3 Florian Best univentionstaff 2017-06-28 14:56:33 CEST
There is a Customer ID set so I set the flag "School Customer affected".
Comment 4 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:25:25 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.
Comment 5 Jan-Luca Kiok univentionstaff 2023-06-23 13:15:25 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.