W3C home > Mailing lists > Public > public-webappsec@w3.org > June 2014

Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)

From: Jesper Kristensen <mail@jesperkristensen.dk>
Date: Sun, 15 Jun 2014 22:44:19 +0200
Message-ID: <539E05A3.7070000@jesperkristensen.dk>
To: Katharine Berry <katharine@getpebble.com>, public-webappsec@w3.org
Den 06-06-2014 07:13Katharine Berry skrev:
> I work at Pebble; we make watches that connect to your phone, and on
> which developers can run code. To be specific, our communication
> scheme for watch development is that the watch connects to an app
> running on the userís phone via Bluetooth. The phone provides a
> websocket server, and our development tools connect to that. We use
> this connection to relay control messages, logs, binaries, etc.
> bidirectionally. The phone mostly acts as a proxy, forwarding messages
> to/from the watch without inspection or modification.
>
> Historically our standard development environment involved a series of
> command-line tools, but this is not user-friendly and is difficult to
> use on Windows. We therefore additionally provide a web-based tool,
> CloudPebble, as a complementary development solution.
>
> The key part here is that CloudPebble must be able to contact the
> watch; hence, it must be able to communicate with the websocket server
> on the phone.

So, you want an app running on your phone to communicate with a website 
running in your browser on your PC, over your local network?

Intuitively, it sound like a use case for WebRTC, not websockets. Have 
you looked at that? (I don't have experience with WebRTC, so I don't 
know if it is actually usable right now)

- Jesper Kristensen
Received on Sunday, 15 June 2014 20:44:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:05 UTC