W3C home > Mailing lists > Public > public-browserext@w3.org > May 2016

Re: Native Messaging (Was: Core API Proposal)

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Tue, 10 May 2016 06:59:41 +0200
To: Andrew Swan <aswan@mozilla.com>
Cc: Rob Wu <rob@robwu.nl>, Florian Rivoal <florian@rivoal.net>, Mike Pietraszak <mikepie@microsoft.com>, "public-browserext@w3.org" <public-browserext@w3.org>
Message-ID: <272caa5c-c3ef-b163-ca68-0251457ab6ca@gmail.com>
On 2016-05-10 06:39, Andrew Swan wrote:
>
> Okay.
>
> To be frank, I'm not sure exactly what you're advocating with respect to the proposed effort to standardize native messaging (the original topic of this thread).  Is it fair to say that you don't think the proposed effort is likely to be useful but that you don't object to it moving ahead?  I'm not trying to put words in your mouth, please correct me if I've got it wrong, but I'd like to have this effort proceed and I think there's some uncertainty lingering over it as a result of this thread...

Hi Andrew,

Since I don't build browsers or operating systems all this are simply my advice and preferences.  The market will (with gratitude) embrace ANY solution that enables platform-level access!  It is even possible that local services running on 127.0.0.1 (which Mozilla et. all is also working on) will eventually kill Native Messaging since such solutions are free from publisher considerations and are simpler to build and deploy.

That is, I still believe that the use-cases for in-browser extensions and native extensions are quite distinct.

Developers are in for a rocky ride :-(

Anders
Received on Tuesday, 10 May 2016 05:08:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:00 UTC