Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Notifications: Ajax Push

Description

The client and agent uses a hanging GET for direct server push notification. This is the 'classic' HTTP solution for server push, but has certain requirements on the server side, which probably are not always given for any environment. I'm no expert in the Comet model, so I don't know in detail how the server needs to be prepared. Advantage would be, that this is a real push and the network flow is still from client to server.

Environment

None

Acceptance Criteria

None

Balsamiq Wireframes

Activity

Show:

Roland Huss September 17, 2011 at 6:33 AM

Comment by Nicholas Whitehead:

I was thinking that if the licenses are compatible, you might want to consider embedding Webbit into Jolokia for these reasons:

  • Probably preferable as the JavaAgent web server than the JVM built in web server.

  • Provides good support for WebSockets (I am guessing you do not want to implement this yourself)

  • Will provide good support for Comet style server push for websocket and non-websocket enabled clients. I am pretty sure it would be possible to capture incoming requests and redirect them to a Webbit instance so that callbacks can be requested and will occur on the same port (mandatory for browser clients). As I see it, something like this would be required when Jolokia does not "own" the listening HTTP port.

Details

Assignee

Reporter

Components

Priority

Created September 17, 2011 at 6:17 AM
Updated September 17, 2011 at 6:48 AM