[aerogear-dev] Non-Native Push Discussion

[Matthias Wessendorf]

On Wed, Apr 10, 2013 at 6:15 PM, Douglas Campos <qmx at 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?
>
> [1]:http://www.w3.org/TR/push-api/


it's under development (spec itself):

https://github.com/telefonicaid/WebAPISpecs


similar to the FirefoxOS Push Network Server:
https://github.com/telefonicaid/notification_server


the client API has interesting notions, but we just can't relay on this
being there, anytime soon (I guess FireFox is little different here)



>
>
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130410/3bd566de/attachment.html