|
Description:
|
The REST endpoints
for receiving messages, should fire
receive HTTP requests in order to perform
a
JMS message
few different "use cases:
* Registration of new Push Application (-> some update/delete is supported too)
Listeners for
* Registration of new Mobile Variant (e.g. SimplePush/Android "app construct" (-> some update/delete is supported too))
* Registration of new Mobile Variant Instance (eg iOS/Android app, running on
the
phone)...
* PushMessage Send-Request to deliver messages to the
particular networks (GCM, APNs, simplePush)
will do
Currently
the
HTTP endpoints are (somewhat) directly performing the storage of the information. Helpers/Services classes are performing the work, but this is all "blocking IO".
Ideally, the HTTP endpoints are just receiving the HTTP requests, quickly publish a Message to a "Message Broker" and immediately return (if possible).
The
actual work
(of storing, via JPA etc) should be then done in a Consumer of a Topic/Queue of the Message broker;
Attached are two _simple_ diagrams, to show the idea...
|
