We're updating the issue view to help you get more done. 

Notification: Push to external URL

Description

In this scenario, the agent on the server side contacts an URL actively when a notification arrives. This URL has been provided by the client when it registers for a notification. Advantage of this solution is that there are no extra requirements for the server where the agent is deployed and that this is a real push as well. However, the flow of communication is reversed, i.e. the agent needs to initiate and issue an HTTP request, which can get quite problematic for certain firewall setups. Also, the result of the push needs to be evaluated on a server as well, so this is not something which will work with every client (e.g. the Javascript client running in a Browser. Of course, WebSockets could be an option here as well).

Environment

None

Acceptance Criteria

None

Status

Assignee

Unassigned

Reporter

Roland Huss

Labels

None

Components

Priority

Major