W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2011

RE: Messaging API and URI schemes (ISSUE-107)

From: Niklas Widell <niklas.widell@ericsson.com>
Date: Fri, 11 Feb 2011 16:53:19 +0100
To: Robin Berjon <robin@berjon.com>, Dominique Hazael-Massieux <dom@w3.org>
CC: Rich Tibbett <richt@opera.com>, public-device-apis <public-device-apis@w3.org>
Message-ID: <6FFCEF6A0AE1D6468ADD4281840995621EC3A05045@ESESSCMS0352.eemea.ericsson.se>
> -----Original Message-----
> From: Robin Berjon [mailto:robin@berjon.com] 
...
> I don't know if it's all that cosmetic. If we use a type we 
> have to define the way in which the other parameters are 
> passed (e.g. to, cc, subject) whereas if we reuse a URI 
> scheme presumably it knows how to carry its own information.
> 
Should the URI be required to carry all info needed? Then we only need a send_msg(URI, attachments_list) method. That would make things simple (or move the headache of creating a correctly encoded URL to the developer). Adding some callbacks will give success/error feedback. 

Best regards,
Niklas
Received on Friday, 11 February 2011 15:53:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:17 GMT