The goal is to dismiss Everrest mechanism which opens Websocket channel to output long-lived async calls and use new JSON-RPC on top of Websockets instead (the one we currently use for FS Watchers and Exec agent).
This should be applied to every side of a triage: client-machine-master.
Proposed tactic is following:
Everrest based Websocket calls - DONEEverrest based Websocket calls - DONEEverrest based Websocket calls - DONEEverrest based Websocket calls - DONEEverrest based Websocket calls - DONEEverrest based Websocket calls - 2d - DONEEWS mechanism/components as deprecated, apply new implementation for UD - Master connection and remove EWS using there in 4 weeks.EWS - ANALYZINGI've added three more tasks (#5522, #5523, #5524) to this epic since several features which use Everrest based Websocket calls were found recently.
I think there are missing clients in the list (like CLI) and maybe others
@benoitf CLI use Websockets ?
@skabashnyuk AFAIK yes
https://github.com/eclipse/che/blob/master/dockerfiles/lib/src/spi/websocket/messagebus.ts
https://github.com/eclipse/che/blob/master/dockerfiles/lib/src/api/wsmaster/workspace/workspace.ts#L124-L134
maybe there are other clients as well
@benoitf Can you take a look https://github.com/eclipse/che/issues/5841? Looks like you are best person for it.
Most helpful comment
I've added three more tasks (#5522, #5523, #5524) to this epic since several features which use Everrest based Websocket calls were found recently.