<div dir="ltr"><div>Yeah, this is a really nice extension I think. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On 2 December 2014 at 08:51, Matthias Wessendorf <span dir="ltr">&lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Dec 2, 2014 at 8:41 AM, Daniel Bevenius <span dir="ltr">&lt;<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span>&gt;<span style="font-family:arial,sans-serif;font-size:13px">Is there a limit how many devices/channels you can aggregate ? </span></span><div>Nothing in the spec that I&#39;ve seen yet, but perhaps some upper bound would be good to have. </div></div></blockquote><div><br></div></span><div>It would be nice for use-cases like:</div><div><br></div><div>My &quot;sports app&quot; subscribes to a game from YOUR_TEAM. A gazillion others do the same.</div><div><br></div><div>One single aggregate channel/endpoint would be cool - because my &quot;Sports backend&#39;, would just have to ping that _one_ endpoint for new payloads.</div><div><br></div><div>With SimplePush, I&#39;d iterate over a gazillion of URLs, performing HTTP_PUT</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-M</div></font></span><div><div class="h5"><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><div class="gmail_extra"><br><div class="gmail_quote">On 2 December 2014 at 08:35, Matthias Wessendorf <span dir="ltr">&lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">interesting screencast.<div><br></div><div>Sounds like way better, than SimplePush. Is there a limit how many devices/channels you can aggregate ? </div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Dec 2, 2014 at 8:10 AM, danielbevenius <span dir="ltr">&lt;<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We have been looking into a companion/extension specification for WebPush<br>
named webpush-aggregate[1], and wanted to share some information about it.<br>
<br>
The webpush-aggregate specification allows for the creation of aggregated<br>
channels. What this means is that it is possible to have multiple channels<br>
that get notified by a single notification request. You can see a<br>
demonstration of this in the provided screen cast [2].<br>
<br>
We still have additional functionality to add from the webpush-aggregate<br>
spec, like handling expiration, updates to the channels in an aggregate etc.<br>
<br>
[1] <a href="http://tools.ietf.org/html/draft-thomson-webpush-aggregate-00" target="_blank">http://tools.ietf.org/html/draft-thomson-webpush-aggregate-00</a><br>
[2]<br>
<a href="https://drive.google.com/file/d/0B2E1HZ1JnrJfcXdtR09WUmJfU3M/view?usp=sharing" target="_blank">https://drive.google.com/file/d/0B2E1HZ1JnrJfcXdtR09WUmJfU3M/view?usp=sharing</a><br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-WebPush-Update-tp10055p10206.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-WebPush-Update-tp10055p10206.html</a><br>
Sent from the aerogear-dev mailing list archive at Nabble.com.<br>
<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><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div>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>
</font></span></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><div class="h5"><br><br clear="all"><div><br></div>-- <br><div>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></div></div>
<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></div>