@TotallyInformation Thanks for the info.
Well, really my question came from the announcement about the developers about the execution timeAPI V2. Where it is said:
"Do not treat this as a fully documented public application - it's a working document
This is a snapshot (March 2018) of the entire HTTP and WebSocket interface between the editor and the runtime and how it correlates with the internal parts of the runtime.
This has been done to help rationalize internal allocations and help stabilize the API. "
That is why I wanted to dispel all doubt that the use of wsockets of the new API is only for communication with the editor.
This is not so "esoteric", some nodejs applications communicate for example with an embedded web-driver, through websockets within the same app. However, although it is transparent to the user, the fact is that machine ports have been opened.
Thank you all.