[aerogear-dev] [WebPush] Update

[Matthias Wessendorf]

On Tue, Dec 2, 2014 at 8:41 AM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> >Is there a limit how many devices/channels you can aggregate ?
> Nothing in the spec that I've seen yet, but perhaps some upper bound would
> be good to have.
>

It would be nice for use-cases like:

My "sports app" subscribes to a game from YOUR_TEAM. A gazillion others do
the same.

One single aggregate channel/endpoint would be cool - because my "Sports
backend', would just have to ping that _one_ endpoint for new payloads.

With SimplePush, I'd iterate over a gazillion of URLs, performing HTTP_PUT

-M




>
> On 2 December 2014 at 08:35, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> interesting screencast.
>>
>> Sounds like way better, than SimplePush. Is there a limit how many
>> devices/channels you can aggregate ?
>>
>>
>>
>>
>> On Tue, Dec 2, 2014 at 8:10 AM, danielbevenius <daniel.bevenius at gmail.com
>> > wrote:
>>
>>> We have been looking into a companion/extension specification for WebPush
>>> named webpush-aggregate[1], and wanted to share some information about
>>> it.
>>>
>>> The webpush-aggregate specification allows for the creation of aggregated
>>> channels. What this means is that it is possible to have multiple
>>> channels
>>> that get notified by a single notification request. You can see a
>>> demonstration of this in the provided screen cast [2].
>>>
>>> We still have additional functionality to add from the webpush-aggregate
>>> spec, like handling expiration, updates to the channels in an aggregate
>>> etc.
>>>
>>> [1] http://tools.ietf.org/html/draft-thomson-webpush-aggregate-00
>>> [2]
>>>
>>> https://drive.google.com/file/d/0B2E1HZ1JnrJfcXdtR09WUmJfU3M/view?usp=sharing
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-WebPush-Update-tp10055p10206.html
>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141202/8cca0c49/attachment.html