On Fri, Mar 22, 2013 at 10:03 AM, Christos Vasilakis
<cvasilak@gmail.com> wrote:
looks nice! +1
some comments:
regarding message format I am more keen in it to be flexible, attaching on it "any" pair that a developer thinks it's appropriate instead of pushing a specific message format.
Any? :) Problem.... it can easily get to large - especially for iOS :)
iOS: The maximum size allowed for a notification payload is 256 bytes;
GCM: The total size of the payload data that is included in a message can't exceed 4096 bytes
From the client perspective and in the future platform specific "client" frameworks we can hide this genericness by providing both platform specific methods e.g notification.addSound().addBadge() as
well as addCustom("my-custom-key") and build out our key-value pair message format.
I guess it's not that simple; I agree at some point we need to differentiate between iOS and Android - however the sending is not generic to a specific client platform. An iOS device can send message to Android (and vice versa). Also not sure if a client SDK really should offer "sound, badge" etc ... that logic should be better handled on the sever.
Sending messages from clients is a bit out of scope, I think - for now;
Thanks
Christos
Hello,
here is a frist draft of the SENDER rest api:
Feedback welcome!
Oh... I am NOT sure if the /URL/ endpoints are named/designed good...
Cheers!
Matthias
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev