Currently, the migration tool's frontend makes HTTP requests each second while the Flowable process is being executed. These requests are handled by the migration REST API and check at what step the Flowable process is. Although this is currently working well enough, we should start using WebSockets as they would be more optimal.
The Dirigible already has an API for WebSockets and we should start using it.
We should consider thoroughly the cases we may need to reconnect the sockets. A possible improvement would be to start using this in the Dirigible.
From xsk created by vmutafov: SAP/xsk#798
Currently, the migration tool's frontend makes HTTP requests each second while the Flowable process is being executed. These requests are handled by the migration REST API and check at what step the Flowable process is. Although this is currently working well enough, we should start using WebSockets as they would be more optimal.
The Dirigible already has an API for WebSockets and we should start using it. We should consider thoroughly the cases we may need to reconnect the sockets. A possible improvement would be to start using this in the Dirigible.