<div dir="ltr">Hello,<div><br></div><div>awesome!<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 13, 2013 at 8:37 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Good News everyone! We have code which registers Android devices to<br>
receive messages from pushee.<br>
It is still very VERY limited, but code which will display a<br>
notification when the app receives a message looks like this:<br>
<br>
<a href="https://gist.github.com/secondsun/242063868b09db030331" target="_blank">https://gist.github.com/secondsun/242063868b09db030331</a></blockquote><div><br></div><div style>the Callback (on r.register()), is success invoked, when PushEE returns HTTP Status 20x (for successful REGISTRATION of the device (aka "MobileVariantInstance"), right?</div>
<div style>Similar, the 'failure' is invoked when PushEE returns any error code (e.g. no connection, or 404 or what ever), right ?</div><div style><br></div><div style><br></div><div style>BTW. is the PushConfig "magically" receiving the regId, from the Intent's onRegistered()? </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
<br>
One of the reservations I've heard is whether or not the PushConfig<br>
object should only have the data sent to pushee in it and put other<br>
configuration elsewhere or if it should be the generic push<br>
configuration object and let AG pick out what it needs to send to pushee.<br></blockquote><div><br></div><div style>I am fine, if the ctor accepts the RegistrationId, if it is clear (e.g. in document, or where else), that it used the intent, like here:</div>
<div style><a href="http://developer.android.com/reference/com/google/android/gcm/GCMBaseIntentService.html#GCMBaseIntentService(java.lang.String..">http://developer.android.com/reference/com/google/android/gcm/GCMBaseIntentService.html#GCMBaseIntentService(java.lang.String..</a>.)<br>
</div><div style><br></div><div style>and _not_ being submitted to the UnifiedPush, when storing the "metadata".</div><div style><br></div><div style>(could be confusing, e.g. when looking at the HTTP /device/register endpoint description - but I may be wrong)</div>
<div style><br></div><div style><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
By unifying into a single config object we make the code simpler/more<br>
approachable. However if we slice it up a bit more finely we can<br>
decouple pushee support from GCM if we want to have an AOSP flavor of<br>
push messaging in the future.<br></blockquote><div><br></div><div style>Not sure... (iOS SDK in mind): Perhaps it's good to keep "PushConfig" for the PushEE-Metadata.</div><div style>That allows us to keep the SenderID for a (later) Convenience Intent? Not sure... mostly thinking out loud </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
wdyt?<br>
<br>
PS and by pushee I mean aerogear-unified-push-server.<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>
</div></div></div>