ah okay. I didnt think of putting the REST service in the config. But
then what would we pass to the REST service as the device token to pass to
aerogear in the subsequent Java call? in the classic push plugin, the
onsuccess(event) came back with a device token that we would then send to
the REST service to register with Aerogear using a Java call.
On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <
ml-node+s1069024n11739h82(a)n5.nabble.com> wrote:
On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
<http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
> Thanks for writing back so quickly!
>
> 1) Can't your "Leatons" REST Service proxy the register request to
the
> push
> server ?
>
> ---Yes that is what we were doing before, the classic push plugin called
> register() which simply registered the token with APNS/GCM, and in the
> onSuccess function we would then send an AJAX call to Leatons REST service
> which would then put the device token we got back from the register() call
> into the Aerogear database using whatever methods Aerogears API exposed
> (sorry, I think that is what I meant by the Sender API)... so if you
> suggest
> using the REST service as a proxy to the push server and bypass the
> register() function altogether, how would we hook up the client
> onNotification() handler?
>
> 2) Or maybe just let Leaton accept the register request made by the
> aerogear
> plugin and store the json payload, later a service can submit that to the
> UnifiedPush Server.
> ---Again, how would we hook up the phonegap client onNotification()
> handler
> if we arent calling register from the clients javascript code??
>
I meant : you still use the plugin javascript code register() but just
make sure that your backend API (Leaton or whatever) accept the path and
the json payload so :
POST http//myleatonservice/rest/registry/device + JSON Payload
You just point to "http//myleatonservice/rest" in you push-config,
"/registry/device" will be added automatically by the plugin.
Could sound hacky but worth to explore.
This way you still hookup your onNotification() handler
>
>
>
> --
> View this message in context:
>
http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific...
> Sent from the aerogear-dev mailing list archive at
Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
[hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific...
To unsubscribe from Android Background push notifications not working, click
here
<
http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=...
.
NAML
<
http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=...