[aerogear-dev] AeroGear Push Message Format

Daniel Bevenius daniel.bevenius at gmail.com
Tue May 28 00:29:18 EDT 2013


>I guess the issue would be on the SPS side and if it can handle receiving
and ignoring the extra info.
This should not be a problemen but let me add a test for this and make sure:
https://issues.jboss.org/browse/AGPUSH-54



On 27 May 2013 23:36, Kris Borchers <kborcher at redhat.com> wrote:

> Unifying the APIs shouldn't be hard and could probably happen sooner
> rather than later, IMO. As far as the client goes, if you send extra info
> beyond the version it will just be ignored. Though, it would be better to
> not send the extra info to keep payload small. I guess the issue would be
> on the SPS side and if it can handle receiving and ignoring the extra info.
>
> On May 27, 2013, at 14:06, Daniel Passos <daniel at passos.me> wrote:
>
> > Very nice!
> > +1 to discuss later how to "unify" APIs
> >
> > Matthias Wessendorf wrote:
> >> We /could/ (later?) try to unify the API and simply
> >> *IGNORE* everything besides the version, when talking
> >> to|SimplePush| Variant.
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130528/f3bc750b/attachment.html 


More information about the aerogear-dev mailing list