REST API Impruve

[koss89]

Good afternoon. The function to control one specific connection is very lacking. With the incoming stream, everything is fine, but for those who watch things are not very good.
I tried to implement control at AdmissionWebhooks level
for example my algorithm.
A request to connect to a stream comes in. I give access, after I need to disconnect all users, I simply delete this stream using the REST API. In this case, AdmissionWebhooks on the direction outgoing with the closed status do not arrive, and this is very bad. From the user's point of view, I can't properly keep track of how much he has watched a given stream.
Then the following situation, let's say I need to turn off not all viewers, but only one, at the moment I do not see the possibility of how to do this.
I saw my suggestion you have inside for each connection there is a certain session identifier. It would be very good if this identifier came along with AdmissionWebhooks at least for direction outgoing and it was possible to delete (disconnect the viewer from the stream) using the REST API by this identifier.
It would also be very good if OME could, for example, once every 5 seconds (configurable parameter) make a repeated request in the form of the same AdmissionWebhooks, and whether this user (session) can still view this stream.
Of course, this request can greatly slow down the server, so it would be possible to implement the ability to enable it only on certain Applications.

Unfortunately, I will most likely have to use NGINX as a reverse proxy for EDGE servers, there is just such an opportunity