[jira] [Created] (ISIS-1176) Provide the capability to push notification messages to end-users without refreshing (using web sockets or Atmosphere etc).

["Dan Haywood (JIRA)" <ji...@apache.org>]

Dan Haywood created ISIS-1176:
---------------------------------

             Summary: Provide the capability to push notification messages to end-users without refreshing (using web sockets or Atmosphere etc).
                 Key: ISIS-1176
                 URL: https://issues.apache.org/jira/browse/ISIS-1176
             Project: Isis
          Issue Type: New Feature
          Components: Core
    Affects Versions: core-1.8.0
            Reporter: Dan Haywood
            Assignee: Dan Haywood
            Priority: Minor
             Fix For: 1.10.0


For example, if an end-user submits a long-running job, then the action should acknowledge the request.  When the job completes then we should provide a mechanism to notify the user (if they are using the system).

The likely technology will be web sockets or Atmosphere; Wicket integrates with both.

One possible design is a persisted entity to hold the messages, keyed by (username, datetime).  We could then have a service that a completing action could call, to save the message.

This service could check if the user is currently logged on, and if so could notify the user via Atmosphere or similar.

I also think it might be nice if the Wicket UI could provide a way for the user to view the last 5 (say) messages, a bit like a notificatoin center.  I think that Mac does this, and Windows 10 will do,  Thus, if the user is *not* logged on when the job completes, then we can still bring the notification message to their attention when they next log on.

Perhaps this could be added as a button on the footer bar?  And/or the messages could slide in from this footer bar.  (This is the way that the MS Azure portal works, and it's not too unpleasant).





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)