sebawagner commented on pull request #67: URL: https://github.com/apache/openmeetings/pull/67#issuecomment-619617460
Yeah I don't mind. I think separating UI view from DB view has also some long term advantages. But just for the sake of this 1 screen. I am not sure how much it is worth. You can potentially make the KStream Serialisable. But it hold all the MediaStream at cetera. I'm not sure how good that would be. I am more keen to get this UI merged, and maybe optimise more later. Cause for me its just a tool to admin and diagnose. And I'm more keen on the diagnosing part. The other part to keep in mind in that we may enhance this also later more. For instance how about using the kurentoClient to compare KStreams with stream on the server ? To discover any leaks ? Or other statistics that you could extract from the MediaServer that may be useful to diagnose https://doc-kurento.readthedocs.io/en/6.7.1/_static/client-jsdoc/module-kurentoClient.KurentoClient.html#~getServerManagerCallback Anyway, lets not make this PR too generic. Its just about adding KStream objects to the list and display "some" details in the right hand panel. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
