Re: [aerogear-dev] Beyond SimplePush's simplicity

FYI, Officially, the predecessor for SimplePush will be WebPush, https://datatracker.ietf.org/wg/webpush/charter/ which runs on top of HTTP2 http://http2.github.io/ Unofficially, data is kind of a pain in the patootie, but obviously really handy to have. There are security and privacy issues a-plenty when dealing with data storage (HIPPA & subpoenas come to mind in the US.) Internally, we're kicking around the idea of allowing data, but not allowing storage, (so a device would only get data if it was actively connected. If it was offline, it would only get the version number update when it reconnected). I'm also interested in what y'all come up with. On 10/20/2014 4:58 AM, Lukáš Fryč wrote: > Hey guys, > > I'm working on a demo of UPS pushing to iOS, Android, Windows, as well > as Firefox OS using our Cordova plugin. > > But as you know, with FFOS it is not that simple - since SimplePush > protocol allows to transfer just incremental versions, we are not able > to deliver any interesting message. > > UnifiedPush Server could be a correct place where we unify and shield > our users from this limitation: > > > my idea is storing the message on UPS under the SimplePush endpoint > URL. Once the message with version reaches the client, he would > contact UPS to retrieve this message under a key ( pushEndpoint, > version ). > > The messages could have default built-in TTL to allow periodic cleanup. > > What do you think? > > > Cheers, > > ~ Lukas > > > _______________________________________________ > 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