<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 19, 2014 at 11:41 AM, 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"><div dir="ltr">Hello Vivek,<div><br></div><div>thanks for the interest in our project<br><div class="gmail_extra"><br><br>
<div class="gmail_quote"><div class="">On Wed, Feb 19, 2014 at 11:34 AM, Vivek Pandey <span dir="ltr"><<a href="mailto:vivek.pandey@pinelabs.com" target="_blank">vivek.pandey@pinelabs.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"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal">
Hello,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">While going through the aerogear-server-push documentation , I could not find an example where we can send a push message using “id” returned by adding a new device token at /rest/registry/device. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Is there a plan to add such a support ?</p></div></div></blockquote><div><br></div></div><div>We have a ticket for that:</div><div><a href="https://issues.jboss.org/browse/AGPUSH-420" target="_blank">https://issues.jboss.org/browse/AGPUSH-420</a><br>
</div><div><br></div><div>but we did not do it, ATM, as this is hard to do for the supported SimplePush bits (e.g. for FirefoxOS).</div><div>We thought about using the device token (e.g. from APNs or the registrationID from GCM), but w/ SimplePush / Mozilla's FirefoxOS this is really an URI.</div>
<div><br></div><div>However, you raised a great point, each installation gets an ID in our database - perhaps we could use that. But that means "your application" needs to store our ID somewhere (in addition to GCM/APNs IDs and Mozilla's Push URI). But I do like the ideas</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"><div class="">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><u></u><u></u></p><p class="MsoNormal">Is relying on unique “alias” a good option to implement the requirement of identifying a device uniquely ?</p>
</div></div></div></blockquote></div></div></div></div></blockquote><div><br></div><div>The benefit of an alias is, that all the devices of a user (e.g. <a href="mailto:mrFoo@company.com">mrFoo@company.com</a>). So, for instance if someone wants to do a google hangout, all of your devices get that message</div>
<div><br></div><div>But, it's for sure of a matter of the actual use-case</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 dir="ltr">
<div><div class="gmail_extra"><div class="gmail_quote"><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"><div class="">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks<u></u><u></u></p><p class="MsoNormal">Vivek<u></u><u></u></p></div>
<br><hr>This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.<hr>
<br></div><br></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><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><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>
</font></span></div></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>