169
edits
CloudServices/Notifications/Specification: Difference between revisions
Jump to navigation
Jump to search
m
CloudServices/Notifications/Specification (view source)
Revision as of 00:02, 17 February 2011
, 17 February 2011→Terminology
m (→Terminology) |
|||
| Line 104: | Line 104: | ||
== Terminology == | == Terminology == | ||
* ''User'': Individual who receives notifications. | [[Image:PN-HighLevelCommLines.png|thumb|250px|High-level overview of the lines of communication between the entities in the system.]] | ||
* ''Client'': One of | |||
* ''Web App'': Third-party web application that actually produces the notifications. The user subscribes to notifications from this app. | * '''User''': Individual who receives notifications. | ||
* '''Client''': One of possibly many devices a user wishes to receive notifications on, e.g. a browser, mobile phone, feather duster, etc. | |||
* '''Web App''': Third-party web application that actually produces the notifications. The user subscribes to notifications from this app via a web page. | |||
* '''Agent''': Responsible for all REST-API calls, this handles the creation of any messages within the message broker on behalf of web apps, and handles the creation of exchanges and queues on behalf of clients. | |||
* '''Routing Key''': A unique identifier generated by the Agent when a user subscribes to notifications from a web app. The routing key is used as a "mailbox address" by the web app to send notifications to the user. | |||
== Server API == | == Server API == | ||