Re: Messaging

Hi Robin, all,

I am fine with option 1 i.e. treating this as a "trusted environment" API for now...

Regards,
Suresh 


----- Original Message -----
From: Robin Berjon [mailto:robin@berjon.com]
Sent: Wednesday, October 20, 2010 07:23 AM
To: public-device-apis@w3.org <public-device-apis@w3.org>
Subject: Messaging

Hi all,

so, what do we do with this Messaging thing?

We have a good looking draft, it's been published for two months without much feedback. More importantly, I still haven't seen a list of use cases for in-browser usage. It is looking like this is a "trusted environment"-only specification.

Should we simply agree that it's that kind of API, thereby giving the editors more freedom with the way in which security is approached, or does someone want to step up with realistic in-browser use cases so that we can figure out where to cut the specification in two?

-- 
Robin Berjon - http://berjon.com/





---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Wednesday, 20 October 2010 14:07:45 UTC