Hello all,
Some of us were pondering over the need of having Web API(s) for health and
similar other sensors. With the growing presence of such sensors on
smart-watches and such, we believe a Web interface for retrieving data from
such sensors is required (especially for Web Apps).
Towards
I'm not sure I understand the problem. Lack of a formal web API doesn't
block these devices from exposing data through web services, does it?
Coming up with a web service or JSON standard for the data would make sense
but that's more of an industry-specific concern that would best be dealt
with
Hello All:
I do not think an API would be the solution for facing the need of
standards in sensors.
I agree, however in the need of a solution -- a kind of standarized
solution -- for the forthcoming trends in data collection.
XML worked pretty well for this half a decade a go or more, I
It's just a more compact data format that happens to evaluate as an object
literal in JS and is perfectly interchangeable with XML and similar data
structures like Python dictionaries. Most modern web services offer both.
You might prefer one or the other, but I can assure that it's perfectly
## Problem
A common desire in web programming is to log any uncaught exceptions back to
the server. The typical method for doing this is
window.onerror = (message, url, line, column, error) = {
// log `error` back to the server
};
When programming asynchronously with promises,
On 9/12/14, 2:34 PM, Domenic Denicola wrote:
Thank you for writing this up. This is definitely an area that needs
improvement.
As usual, if one or both of these events is missing listeners, nothing will
happen.
I'm not sure that's usual.
Specifically, an observable case that's worth
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky
As usual, if one or both of these events is missing listeners, nothing will
happen.
I'm not sure that's usual.
I think I misspoke here. The events will still be fired! Anything else would be
insanity. I just
On 9/12/14, 3:19 PM, Domenic Denicola wrote:
If there is no listener for either when the promise would normally fire error, but then a
listener for rejectionhandled gets added before a .catch() call on the
promise, does the listener get called?
No.
That's not compatible with the events
From: Boris Zbarsky [mailto:bzbar...@mit.edu]
On 9/12/14, 3:19 PM, Domenic Denicola wrote:
If there is no listener for either when the promise would normally fire
error, but then a listener for rejectionhandled gets added before a
.catch() call on the promise, does the listener get called?
On 9/12/14, 3:45 PM, Domenic Denicola wrote:
var p = Promise.reject(new Error(boo));
setTimeout(() = {
window.onrejectionhandled = () = console.log(got here);
}, 100);
setTimeout(() = {
p.catch(() = {});
}, 200);
That's a good proxy for what I was envisioning...
In this case the
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky
In this case the event would be fired
By the event do you mean the error event or the rejectionhandled event?
Ah, trick question! Because, see, I was confused when I wrote that, and myself
did not know!
but no
Erik Reppen erik.rep...@gmail.com writes:
It's just a more compact data format that happens to evaluate as an object
literal in JS
Not always: http://timelessrepo.com/json-isnt-a-javascript-subset
--
Nils Dagsson Moskopp // erlehmann
http://dieweltistgarnichtso.net
I believe a way to directly read health data into web apps with a browser
api (JavaScript) is an interesting idea. You could then have a webrtc video
conference with your doctor and he could read out your pulse and other
health data directly from your device live and give you an opinion. Seeing
as
Hi All:
Use and transmission of private/personal Health data, as other sensitive
personal data, is ruled by law and regional regulations in some -- or in
most of the -- developed countries.
Please, take this aspect in consideration.
* I would not recommend to read health data within
Browsers have been dealing with private personal data for a while now, that
includes video camera microphone input, geolocation and more. Health data
isn't so different in that respect. There are mechanisms to deal with
privacy already in the browser. But indeed: a spec would need to consider
hello all:
please, might you point me some were I can find part of this solutions (
ie video/audio encrypt . That would be really helpful to me.
br
---
Delfin Ramirez
+34 633 589231
del...@segonquart.net [4]
twitter: delfinramirez
IRC: segonquart Skype: segonquart [5]
Search for webrtc.
Best Regards,
Silvia.
On 13 Sep 2014 09:57, delfin del...@segonquart.net wrote:
hello all:
please, might you point me some were I can find part of this solutions (
ie video/audio encrypt . That would be really helpful to me.
br
---
Delfin Ramirez
+34 633 589231
On 9/12/14, 4:07 PM, Domenic Denicola wrote:
To state what happens in that scenario more clearly:
- `error` is fired at time zero. Nobody is listening.
- `rejectionhandled` is fired at time 200 ms. Somebody is listening, and got
here is logged.
OK, good. We're on the same page!
-Boris
That's a stronger argument than I would have thought of (and mind you I'm
just a lurker without anything in the way of influence so don't let me
shoot you down or anything). But audio/video capture is a general
media/communication thing.
To me it's like the difference between geolocation and
What I'd you're a long way away from any medical help?
In my mind this is part of the larger drive of the web of things (IoT
applied to the web) and needs device APIs. This might not be the right
group to discuss it in though.
Best Regards,
Silvia.
On 13 Sep 2014 10:53, Erik Reppen
20 matches
Mail list logo