Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #34285
| Newsgroups | comp.lang.java.programmer |
|---|---|
| Date | 2016-05-11 19:11 -0700 |
| References | <a2d8c4d6-bf81-4338-a74f-5f7b77ec8a6e@googlegroups.com> |
| Message-ID | <bd26dec3-14c2-4bbf-a6e4-65fec05a2fba@googlegroups.com> (permalink) |
| Subject | Re: JAVA Server and WebApp future and People Power |
| From | maherrj@googlemail.com |
On Friday, February 19, 2016 at 10:04:39 AM UTC+8, mah...@googlemail.com wrote: > I beg all of you who are interested in the growth of HTML5 functionality and the future of browser-hosted web-apps to read the following: - > > https://github.com/w3c/geofencing-api/issues/25 > https://github.com/slightlyoff/ServiceWorker/issues/745 > > The currently proposed geofencing design current ignores the need for a holistic server-based solution. > > I understand the concerns about privacy and battery-life and am more than happy to address them in a lively debate. A victory for common sense. Excellent news! On Thu, May 12, 2016 at 2:40 AM, Marijn Kruisselbrink <mekATchromium.org> wrote: For quite a while now the geofencing API hasn't been much of a priority for us. Now in addition to that we're no longer convinced the geofencing API in its current shape is the best way to address the use cases we're interested in addressing. So with that in mind we've decided to stop work on the geofencing API in its current form. Marijn Combine that outcome with this at the upcoming TPAC: - Hello All, The registration for TPAC 2016 is now open - relevant information is provided in the email attachment below. There will not be a stand-alone meeting for the Geolocation Working Group, but there will likely be a joint meeting between the Geo WG and the Devices and Sensors (DAS) WG. This should be confirmed soon, and will take place during the DAS WG's allocated meeting time (Sep. 19-20). Thanks, -Giri Mandyam, Geolocation Working Group Chair An the scene is set for a ServiceWorker.TravelManager.subscribe() outcome or, more likely, a generic sensor.AddListener(filterOptions). Either way these are exciting times indeed. Good Luck!
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
JAVA Server and WebApp future and People Power maherrj@googlemail.com - 2016-02-18 18:04 -0800
Re: JAVA Server and WebApp future and People Power Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2016-02-21 08:02 +0800
Re: JAVA Server and WebApp future and People Power maherrj@googlemail.com - 2016-05-11 19:11 -0700
Re: JAVA Server and WebApp future and People Power maherrj@googlemail.com - 2016-05-22 17:42 -0700
csiph-web