<br><br><div class="gmail_quote">On Fri, Mar 22, 2013 at 10:03 AM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">looks nice! +1<div><br></div><div>some comments:</div><div><br></div><div>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. </div>
</div></blockquote><div><br></div><div>Any? :) Problem.... it can easily get to large - especially for iOS :)</div><div><br></div><div>iOS: The maximum size allowed for a notification payload is 256 bytes;</div><div>GCM: The total size of the payload data that is included in a message can't exceed 4096 bytes</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div> 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 </div>
</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>well as addCustom("my-custom-key") and build out our key-value pair message format. </div>
</div></blockquote><div><br></div><div>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.</div>
<div><br></div><div>Sending messages from clients is a bit out of scope, I think - for now;</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div>Christos</div><div><br></div></font></span><div><div><div><br></div><div><br><div><div><div class="h5"><div>On Mar 21, 2013, at 5:30 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div>
<br></div></div><blockquote type="cite"><div><div class="h5">Hello,<div><br></div><div>here is a frist draft of the SENDER rest api:</div><div><br></div><div><a href="https://gist.github.com/matzew/b21c1404cc093825f0fb" target="_blank">https://gist.github.com/matzew/b21c1404cc093825f0fb</a></div>
<div>
<br></div><div>Feedback welcome!</div><div><br></div><div>Oh... I am NOT sure if the /URL/ endpoints are named/designed good...</div><div><br></div><div>Cheers!</div><div>Matthias</div><div><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div></div><div class="im">
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>