<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 24, 2013 at 4:30 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 class="im"><br>
On May 24, 2013, at 9:24 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
<br>
> I have 2 small questions about the simplePushServer which are not crystal clear for me :<br>
><br>
> 1. When sending a notification, looks like, SPS only sends it to one User Agent (I can't find the "broadcast" logic), does that mean that UP has to do 1 PUT request to SPS per user agent ?<br>
<br>
</div>Yes. Broadcast is something we added via UP. It is not part of the SPS spec.<br>
<div class="im">> 1.a is a channel always associated to 1 user agent ?<br>
<br>
</div>Yes<br></blockquote><div><br></div><div><br></div><div style>think your private email account :)</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 class="im">><br>
> 2. Does the content of the notification really only contains a version number ? (How do we pass other info, or is it just a trigger and the responsability of the UA to request to an app server the info?<br>
<br>
</div>Yes, only version. That is why it's called "Simple". It is meant only to inform the app that new information is available for a particular channel and it is up to the app to decide what to do with it. That way, the app has choices. It could immediately fetch the new data, it could prompt the user that new data is available, etc.<br>
><br>
> Thanks<br>
> Seb<br>
><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>
<br>
<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>