Regarding SimplePush/WebPush : is WebPush to be considered (in the future)

Thanks ! The screencast helps a lot to understand all the concepts in 3 minutes. Regarding SimplePush/WebPush : is WebPush to be considered (in the future) as replacement of SPS ? Will SPS be deprecated ? What will FirefoxOS be using ? Sebi On Thu, Nov 20, 2014 at 9:36 AM, Daniel Bevenius < daniel.bevenius(a)gmail.com&gt; wrote: > We've been looking into the WebPush specification[1] a little closer and > thought we should share some info about it. > > We created a simple proof of concept to get a better understanding of the > specification which can be found here: > https://github.com/danbev/aerogear-webpush-server > > The README.md contains more details regarding the specification and there > is a 3 min screen cast [2]. > > > [1] https://tools.ietf.org/html/draft-thomson-webpush-http2-01 > [2] > https://drive.google.com/file/d/0B2E1HZ1JnrJfYW90eVBTaGkzSkU/view?usp=sha... > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Is there a limit how many devices/channels you can aggregate ?

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(a)gmail.com&gt; 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=sha... > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-WebPush-Update-tp1... > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Tue, Dec 2, 2014 at 8:41 AM, Daniel Bevenius <daniel.bevenius(a)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(a)apache.org&gt; > 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(a)gmail.com&gt; 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=sha... >>> >>> >>> >>> -- >>> View this message in context: >>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-WebPush-Update-tp1... >>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)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(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev