I updated the GIST and added that UBER API, for discussions:<div><br></div><div><a href="https://gist.github.com/matzew/2da6fc349a4aaf629bce#convenience-uber-api">https://gist.github.com/matzew/2da6fc349a4aaf629bce#convenience-uber-api</a></div>
<div><br></div><div><br></div><div>-Matthias<br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 2:41 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><div class="im">On Wed, Mar 20, 2013 at 2:13 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe we can have this UBER api but we still need to have the "atomic" service to be able to add a mobile apps afterwards, no ? <div>Second point is, if I understood it well from the previous gists and discussion : inside a same device type, let's say iOS, there can multiple mobile apps pointing to the same push app (freemium/premium etc ...). So we need an extra array : </div>
<div><br></div><div><br></div><div><div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif">[</div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif">
{</div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif"> name: "app1",</div></div></div></blockquote></div><div>..... </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif"><span style="font-size:12.727272033691406px"> name: "app2",</span></div></div></div></blockquote>
<div><br></div><div>... not sure if I really want to register the entire app store, with one HTTP POST :)</div><div><br></div><div>what u suggested is basically, one POST registers:</div><div>-Foo-Inc's HR app (and various iOS/Android)</div>
<div>-Foo-Inc's CRM app (and various iOS/Android)</div><div>-Foo-Inc's WHAT-NOT-APP app (and various iOS/Android)</div><div>...</div><div><br></div><div>I think that a POST to /applications, should only register ONE push app (however, with different mobile variations (paid/free))</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div><br></div><div>-M</div></font></span><div><div class="h5"><div><br></div><div><br></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><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif">
<div><div> description: "desc2",</div><div> // I would recommend wrapping these in platform names in case key names ever change and match</div><div> ios: {</div><div>
[</div></div><div> {cert: "certval3",</div><div> passphrase: "passphrase3"},</div><div><br></div><div> {cert: "certval4",</div><div> passphrase: "passphrase4"}</div>
<div> ] </div><div> },</div><div>android: {</div><div> [</div><div> {"google-api-key": "key3"},</div><div> {"google-api-key": "key4"}</div><div> ] </div>
<div>}</div><div> }</div><div>]</div></div></div><div><div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif"><br></div><div style="color:rgb(34,34,34);font-size:12.727272033691406px;font-family:arial,sans-serif">
<br></div><div><br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 1:54 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.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"><br><div><div><div><div>On Mar 20, 2013, at 7:42 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite">
<br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 1:31 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.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"><br><div><div><div>On Mar 20, 2013, at 6:43 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br></div><blockquote type="cite">
<div>Here is the REST API for "Push App" (+mobile app) registrations:<div><br></div><div><a href="https://gist.github.com/matzew/2da6fc349a4aaf629bce" target="_blank">https://gist.github.com/matzew/2da6fc349a4aaf629bce</a></div>
<div>
<br></div><div><br></div><div>Questions:</div><div><br></div><div>The post to "/applications/das231432qwdsa2/iOS" and/or "/applications/das231432qwdsa2/android" are different (payload-wise)....</div><div>
<br></div><div>Not sure if that is best solution.... However, we need to differentiate between different "mobile os variants" anyways....</div><div><br></div></div><div>My (CURRENT) feelings is that a different "endpoint" is better instead of an ugly, large - but generic - API that does everything, and the server figures out what type of mobile app has been registered …</div>
</blockquote><div><br></div>I agree that different endpoints makes sense, especially if a user is only interested in iOS devices for example and so only build an app that works on iOS, since this would allow for easy registration of a single type of application. I would however like to see, and believe users would like to see, some sort of unified API so that they only have register an app once for both Android and iOS. Maybe this won't be an issue once we have more than just a REST interface but just wanted to throw it out there.<br>
</div></div></blockquote><div><br></div><div><br></div><div>Like a post to "/applications</div><div><br></div><div>where the payload is:</div><div><br></div><div><div>{</div><div> // push app properties</div><div> "description":"just a test",</div>
<div> "name":"TestApp",</div><div> </div><div> // REQUIRED Apple Push Network props:</div><div> "cert":"CERT_UPLOAD_VAL",</div><div> "passphrase": "top-secret",</div>
<div> </div><div> REQUIRED GCM Push Network props:</div><div> "google-api-key": "dsdsaadsadsdasadsdsa" </div><div> </div><div>}</div><div><br></div><div>and the 201 Response could look like:</div>
<div>
{</div><div> "id":"PushAppKey"</div><div> "apps":[</div><div> {"iOS-ID":"adda213213"},</div><div> {"android-ID":"454dda213213"},</div><div> ]</div>
<div>}</div><div><br></div><div>This UBER :) API could work, for really just one "server side" abstraction, that has exaclty ONE iOS and one Android APP (of course the request body of the POST could contain arrays for different CERTS, passphrases, API-Keys).</div>
<div><br></div><div>For a convenience we surly can have that - Is that what you mean ?</div></div></div></blockquote><div><br></div></div></div>Yep, that is pretty much what I meant, and would be in favor of passing an array of applications instead of an array of certs, etc. which would allow for multiple applications on multiple platforms like this:</div>
<div><br></div><div>[</div><div> {</div><div> name: "app1",</div><div> description: "desc1",</div><div> // I would recommend wrapping these in platform names in case key names ever change and match</div>
<div> ios: {</div><div> cert: "certval1",</div><div> passphrase: "passphrase1"</div><div> },</div><div> android: {</div><div> "google-api-key": "key1"</div><div> }</div><div>
},</div><div><div> {</div><div> name: "app2",</div><div> description: "desc2",</div><div> // I would recommend wrapping these in platform names in case key names ever change and match</div><div> ios: {</div>
<div> cert: "certval2",</div><div> passphrase: "passphrase2"</div><div> },</div><div> android: {</div><div> "google-api-key": "key2"</div><div> }</div><div> }</div></div><div>
]<br><blockquote type="cite"><div><div><div class="gmail_quote"><div><div><br></div><div>-M</div></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><blockquote type="cite"><div><div>
<div><br></div><div><br></div><div>NEXT: Device Registrations + Sender Endpoints</div><div><br></div><div>(Followed by "management" (get, put, delete.....)</div><div><br></div><div> </div><div>Greetings,</div><div>
Matthias</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Mar 19, 2013 at 4:45 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px">Hello,</span></font><div>
<font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px"><br>
</span></font></div><div><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px">here is the 'overview' section of the Unified push....:<br></span></font><div><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px"><br>
</span></font></div><div><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px"><br></span></font><h1 style="font-size:28px;margin:0px 0px 10px;padding:0px;font-family:Helvetica,arial,freesans,clean,sans-serif">
AeroGear Unified Push (DRAFT 0.0.2)</h1><p style="margin:0px 0px 15px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">This is an <em>early</em> version of a 'spec' for the AeroGear Unified Push server.</p>
<h2 style="margin:20px 0px 10px;padding:0px;font-size:24px;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204,204,204);font-family:Helvetica,arial,freesans,clean,sans-serif"><a name="13d8808bfd064448_13d87ef21dc99431_13d87de08faaf0a3_13d87c8ffc9079b9_13d83534f6ebf0be_overview" href="https://gist.github.com/matzew/ec5c3c2dfa955c58c328#overview" style="color:rgb(65,131,196);text-decoration:none;display:block;padding-left:30px" target="_blank"></a>Overview</h2>
<p style="margin:0px 0px 15px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">The <em>Unified Push</em> solution contains the following components:</p><ul style="margin:15px 0px;padding:0px 0px 0px 30px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">
<li>Native Push Component: <em style="margin-top:0px">sends native push message to registered apps</em></li><li>Web Push Component: <em style="margin-top:0px">sends web push message to online client (e.g. WebSocket/SockJS clients)</em></li>
<li>Client SDK API<ul style="margin:0px;padding:0px 0px 0px 30px"><li>Native Push Client for iOS</li><li>Native Push Client for Android</li><li>Web Push Client for JavaScript</li></ul></li></ul><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">
Details are discussed on the each of the different components</p><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">
<br></p><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">NOTE: LINK need to be enabled :) :)</p>
<p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">HOWEVER.......</p><p style="margin-top:15px;margin-right:0px;margin-left:0px;margin-bottom:0px!important">
<font face="Helvetica, arial, freesans, clean, sans-serif"><span style="line-height:20px">Here is what I'd like to add to the home page for the native push component - based on last weeks </span></font><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px">discussion</span></font><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="line-height:20px">:</span></font></p>
<p style="margin-top:15px;margin-right:0px;margin-left:0px;margin-bottom:0px!important"><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px"><a href="https://gist.github.com/matzew/69d33a18d4fac9fdedd4" target="_blank">https://gist.github.com/matzew/69d33a18d4fac9fdedd4</a></span></font></p>
<p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">PLEASE comment on the gist....</p>
<span><font color="#888888"><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important"><br>
</p><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">
<br></p><p style="margin-top:15px;margin-right:0px;margin-left:0px;font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important"><br></p><br>-- <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><br>
</font></span></div></div>
</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>
</div></div></div>
_______________________________________________<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></blockquote>
</div><br></div><br>_______________________________________________<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><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>
</div></div>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
_______________________________________________<div><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><br>_______________________________________________<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><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<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><br></blockquote></div></div></div><div class="HOEnZb"><div class="h5"><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>
</div></div></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>
</div>