[aerogear-dev] AeroGear Push Message Format

[Matthias Wessendorf]

On Mon, May 27, 2013 at 11:36 PM, 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.


if we do ignore the extra info, than it would be ignored on the UnifiedPush
side.
If the SimplePush variant type, the server would just send the version, and
not everything else.  I don't see a reason to send the entire message,
unfiltered, to the SP-server



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



-- 
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/20130528/29d26c12/attachment.html