[Info-vax] VMS Server and WebApp future and People Power

[Stephen Hoffman]

On 2016-02-19 02:07:20 +0000, maherrj at googlemail.com said:

> 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: -
...
> The currently proposed geofencing design current ignores the need for a 
> holistic server-based solution.  That server will be JAVA, C#, or VMS 
> 3GL?

You forgot to include artisanal and crafted from the finest organic 
bits, there.

I have no idea what you're on about here either, Richard.

Unless you're thinking of running location or other services in the 
background on a server?  Because from the (usual) server view of this 
stuff, the server downloads the Javascript, and the Javascrupt 
retrieves the data from the client.   
http://www.codediesel.com/javascript/adding-html5-geolocation-to-your-applications/ 
 Etc.   I'm guessing that some folks on this committee — not really 
wanting to wade through a couple of large piles of discussions 
previously referenced, either — are looking at the server performing 
pushes to either retrieve the data from the client, or to establish a 
geofence to trigger some activity on the client, or maybe the client 
sends a push back to the server when the geofence is exceeded, with the 
Javascript running in the background?

Sending nasynchronous otifications to a server is comparatively easy, 
too.   Most servers being far less communications- and 
resource-constrained than mobile, battery-powered clients, after all.

> I understand the concerns about privacy and battery-life and am more 
> than happy to address them in a lively debate.

I too understand the concerns, being quite dependent on mobile devices, 
and do use location services, geofences and push.   Location services 
and geofencing are (obviously) already available on mobile devices, 
through native apps, and those can (obviously) be backgrounded.  Those 
links appear to be the HTML5 committee sorting out how to add those 
same capabilities into web browser clients, allowing those capabilities 
in the background.

Not clear what any of that has to do particularly with OpenVMS, nor why 
I'd particularly want to go engage a W3C committee on this topic.   
They'll either sort this out, or they won't.  I can get what I need 
here with a native client, though that approach is clearly more of a 
hassle than a Javascript web client.   Or I can get what I want here 
with JSON or some other web API on the server, for that matter.   Not 
that OpenVMS has any idea how to spell GPS or geofence, nor any 
particular idea how to secure or control these requests except entirely 
through application code.






-- 
Pure Personal Opinion | HoffmanLabs LLC