You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2019. It is now read-only.
For long-running EOperations add support of WebSocket creation (leverage existing websocket routing functionality). Create an instanceof IProgressMonitor which would send/receive commands over the WebSocket (look for simple message interface in the existing code/examples). On the browser side have a promise backed by the web socket and wired to the progress monitor methods. Maybe have a standard operation invocation page displaying the monitor, cancel button, and the result when the monitor is done.
Something like this:
Input form submit button disables the form, creates a web socket and makes the progress bar and log item list visible.
Progress notifications are dispatched to the progress bar (completion percentage) status well (current task/subtask) or log items list depending on progress notification type attribute.
When the promise is resolved or rejected the result or rejection message are displayed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For long-running EOperations add support of WebSocket creation (leverage existing websocket routing functionality). Create an instanceof IProgressMonitor which would send/receive commands over the WebSocket (look for simple message interface in the existing code/examples). On the browser side have a promise backed by the web socket and wired to the progress monitor methods. Maybe have a standard operation invocation page displaying the monitor, cancel button, and the result when the monitor is done.
Something like this:
type
attribute.The text was updated successfully, but these errors were encountered: