Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-7361

Push: Integration of CDI to decouple HTTP endpoints (for sending)

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None

      The REST endpoints receive HTTP requests in order to perform a few different "use cases:

      • PushMessage Send-Request to deliver messages to the particular networks (GCM, APNs, simplePush)

      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...

        1. JMS_Send.gliffy
          24 kB
          Matthias Wessendorf
        2. JMS_Send.png
          26 kB
          Matthias Wessendorf
        3. JMS_Registration.gliffy
          67 kB
          Matthias Wessendorf
        4. JMS_Registration.png
          45 kB
          Matthias Wessendorf

            Unassigned Unassigned
            mwessend@redhat.com Matthias Wessendorf
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: