Re: [aerogear-dev] Non-Native Push Discussion
On Apr 10, 2013, at 11:15 AM, Douglas Campos <qmx(a)qmx.me> wrote:
On Wed, Apr 10, 2013 at 06:41:20AM -0500, Kris Borchers wrote:
> ## Client Side
>
> The client will also be very flexible in relationship to native push.
> Again, since there is no real standard for NNP, the client should be
> built to accept what ever unified payload is designed to work for the
> native push. That way this will again provide for seamless integration
> with the unified push. The client will be built as an adapter of
> Notifier allowing an AeroGear user to manage all notification
> messaging (Push, Pub/Sub, etc) in one place. This means that the spec
> and APIs for Notifier need to be decided and documented before or at
> the same time as the NNP is being developed.
How does the Push API[1] fits here?
I need to read this spec more thoroughly (which I am doing now) but we should probably
follow it for easier integration when browsers actually start to support this stuff
natively.
[1]:http://www.w3.org/TR/push-api/
--
qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev