Skip to content
This repository has been archived by the owner on Feb 22, 2019. It is now read-only.

WebSocket EOperation and IProgressMonitor parameter #29

Open
pvlasov opened this issue May 6, 2017 · 0 comments
Open

WebSocket EOperation and IProgressMonitor parameter #29

pvlasov opened this issue May 6, 2017 · 0 comments

Comments

@pvlasov
Copy link
Member

pvlasov commented May 6, 2017

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:

  1. Input form submit button disables the form, creates a web socket and makes the progress bar and log item list visible.
  2. 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.
  3. When the promise is resolved or rejected the result or rejection message are displayed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant