Bug 848167 - RFE: Add support for pushing notifications from server to web client/UI
Summary: RFE: Add support for pushing notifications from server to web client/UI
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server, Core UI (Show other bugs)
(Show other bugs)
Version: 4.4
Hardware: Unspecified Unspecified
high vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2012-08-14 19:30 UTC by John Sanda
Modified: 2015-02-06 01:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description John Sanda 2012-08-14 19:30:43 UTC
Description of problem:
There are scenarios involving asynchronous work flows that make reporting errors to the UI difficult at best. One such situation came up in bug 828568. The user manually imports resources from the discovery queue. The server then kicks off a job that runs asynchronously. This job notifications the agent of inventory status changes for the imported resources. If the agent cannot be reached, an exception is logged, but we have no good way right now of reporting that in the UI. This is a perfect use case for something like Errai which would allow us to push event notifications from server to the UI.

Plugin deletion is another example. Once you delete a plugin, you can then purge it to completely remove it from the system. The purge happens asynchronously. The only way for the user to know if/when the purge has completed is to continually refresh the page or check the server logs. A server-to-UI event notification mechanism is sorely needed here as well.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Note You need to log in before you can comment on or make changes to this bug.