<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">the same will probably happen with iOS when adding in safari push<br><div><div>On Jul 16, 2014, at 12:53 PM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi ! <div>This is just an idea (for later/future) I had when I looked at the Amazon Device Messaging bits (the GCM variant from Amazon). </div><div><br></div><div>Basically it's just Java/Android code : <a href="https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm">https://developer.amazon.com/public/apis/engage/device-messaging/tech-docs/04-integrating-your-app-with-adm</a></div>
<div><br></div><div>But when we will implement the UPS Amazon library there will be some duplication (basically the UPS registration process). </div><div><br></div><div>It would be nice if this was extracted into a small module (i.e : android-unifiedpush-registration) that could be used by the "pure" android bits (i.e : android-unifiedpush-gcm) and by the Amazon bits (android-unifiedpush-adm) and maybe later by other system based on Android but using their own Push infra.</div>
<div><br></div><div>wdyt ? </div><div><br></div><div>Sebi</div><div><br></div><div><br></div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>