Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Network Web Sockets allow web pages, native applications and devices to create encrypted Web Socket networks by discovering, binding and connecting peers that share the same channel name in the local network.

Channel names can either be:

Common, memorable strings such as e.g. "webchat" to allow any service to connect to a public channel, or:
Pseudo-secure strings such as randomly-generated hashes e.g. "cJWHi8q7SvNWAiSerpfxW3inYjXiKNqR" that are known and shared out-of-band between two or more actors to connect to a private channel.

Network Web Sockets prevents channel name discovery and channel message injection by snooping on the traffic in the local network. This is achieved using the mechanisms described in our DNS-based Secure Service Discovery (DNS-SSD) draft and encrypting all communications between participating nodes within different channels.

Any channel within the Network Web Sockets ecosystem is considered as secure as its out-of-band key sharing mechanisms (whether that is on a public forum online or via other more secure sharing mechanisms). If a channel key is available to a user, then that user will be able to join that channel (although nothing stops channels performing additional authentication over the channel whenever a new peer connects). Similarly, if a user is unaware of a channel name, they will have no way of discovering that channel name via any traffic flowing in the local network.

Web pages, native applications and devices can create ad-hoc inter-applicaton communication bridges between and among themselves for a variety of purposes:

For discovering matching peer services on the local device and/or the local network.
To create full-duplex, encrypted communications channels between network devices, native applications and web applications.
To create full-duplex, encrypted communication channels between web pages on different domains.
To import and export data between network devices, native applications and web applications.
To create initial local session signalling channels for establishing P2P sessions (for e.g. WebRTC signalling channel bootstrapping).
To establish low latency local network multiplayer signalling channels for games.
To enable collaborative editing, sharing and other forms of communication between different web pages and applications on a local device or a local network.

A web page or application can create a new Network Web Socket by choosing a channel name (any alphanumeric name) via any of the available Network Web Socket interfaces. When other peers join the same channel name then they will join all other peers in the same Network Web Socket broadcast network.

You can read more about the secure discovery process and proxy-to-proxy encryption used by Network Web Sockets on this wiki page.

Getting started

This repository contains an implementation of a Network Web Socket Proxy, written in Go, required to use Network Web Sockets.

You can either download a pre-built Network Web Sockets binary or build a Network Web Socket Proxy from source to get up and running.

Once you have a Network Web Socket Proxy up and running on your local machine then you are ready to create and share your own Network Web Sockets. A number of Network Web Socket client examples are also provided to help get you started.

Download a pre-built platform binary

How to build from source

Network Web Socket Interfaces

Local HTTP Test Console

Once a Network Web Socket Proxy is up and running, you can access a test console in your web browser and play around with Network Web Sockets at http://localhost:9009.

JavaScript Interfaces

The Network Web Sockets JavaScript polyfill library exposes a new JavaScript interface on the root global object for your convenience as follows:

NetworkWebSocket for creating/binding named websockets to share on the local network.

You must include the polyfill file in your own projects to create these JavaScript interfaces. Assuming we have added the Network Web Sockets JavaScript polyfill to our page then we can create a new NetworkWebSocket connection object via the JavaScript polyfill as follows:

// Create a new Network Web Socket peer in the networkvarws=newNetworkWebSocket("myChannelName");

We then wait for our peer to be successfully added to the network:

ws.onopen=function(){console.log('Our channel peer is now connected to the `myChannelName` web socket network');};

We can listen for incoming broadcast messages from channel peers in the network as follows:

ws.onmessage=function(event){console.log("Broadcast message received: "+event.data);};

We can send broadcast messages to all the other currently known channel peers in the network as follows:

ws.send('This is a broadcast message to *all* other channel peers');

When we create a Network Web Socket connection object then the Network Web Socket Proxy will start to discover and connect to all other myChannelName channel peers that are being advertised in the local network.

Each time a new channel peer is discovered in the network a Web Socket proxy connection to that peer is established and a new connect event is queued and fired against our root Network Web Socket object:

ws.onconnect=function(event){console.log('Another peer has been discovered and connected to our `myChannelName` web socket network!');};

In this connect event, we are provided with a direct, peer-to-peer Web Socket connection object that can be used to communicate directly with this newly discovered and connected peer.

We can send a direct message to a channel peer and listen for direct messages from this channel peer as follows:

// Wait for a new channel peer to connect to our `myChannelName` web socket networkws.onconnect=function(event){// Retrieve the new direct P2P Web Socket connection object with the newly connected channel peervarpeerWS=evt.detail.target;// Wait for this new direct p2p channel connection to be openedpeerWS.onopen=function(){// Listen for direct messages from this peerpeerWS.onmessage=function(event){console.log("Direct message received from ["+peerWS.id+"]: "+event.data);}// Send a direct message to this peerpeerWS.send('This is a direct message to the new channel peer *only*'):
};};

With both broadcast and direct messaging capabilities it is possible to build advanced services on top of Network Web Sockets. We are excited to see what you come up with!

Web Socket Interfaces

Devices and services running on the local machine can register Network Web Sockets without needing to use the JavaScript API. Thus, we can connect up other applications and devices sitting in the local network such as TVs, Set-Top Boxes, Fridges, Home Automation Systems (assuming they run their own Network Web Socket Proxy client also).

To create a new Network Web Socket connection to a channel from anywhere on the local machine (i.e. to become a 'channel peer') you can establish a Web Socket connection to a running Network Web Socket Proxy at the following URL:

ws://localhost:<port>/<channelName>

where:

port is the port on which your Network Web Socket Proxy is running (by default, 9009),
channelName is the name of the channel you want to create, and;

Messages sent and received on this Web Socket connection have a well-defined data format.

This Web Socket connection will notify you when channel peers connect and disconnect from <channelName> and when broadcast or direct messages are sent to you from other connected channel peers. This Web Socket connection can also be used to send broadcast or direct messages toward all other connected channel peers.

When a new channel peer connects to <channelName> on the network a new message is sent to your connection as follows:

{action: "connect",// a new channel peer has connected to <channelName>source: "<you>",// your channel peer's idtarget: "<newPeerId>"// the unique id of the new channel peer connection}

Similarly when a channel peer disconnects from <channelName> on the network a new message is sent to your connection as follows:

{action: "disconnect",// an existing channel peer has disconnected from <channelName>source: "<you>",// your channel peer's idtarget: "<existingPeerId>"// the unique id of the existing channel peer connection}

To send a broadcast message to all other connected channel peers you can send it over your connection as follows:

{action: "broadcast",// this is a sent broadcast messagedata: "<data>"// the data you want to send to all other channel peers}

When receiving a broadcast message from another connected channel peer it is sent to you over your connection as follows:

{action: "broadcast",// this is a received broadcast messagesource: "<peerId>",// the sending channel peer's iddata: "<data>"// the data you want to send to all other channel peers}

To send a direct message to another channel peer, bypassing the broadcast channel, you can send it over your connection as follows:

{action: "message",// this is a sent direct messagetarget: "<recipient>",// the id of an existing channel peer you want to send a direct message todata: "<data>"// the data you want to send to <recipient>}

When receiving a direct message from another channel peer, that has bypassed the broadcast channel, it is sent to you over your connection as follows:

{action: "message",// this is a received direct messagesource: "<sender>",// the id of the channel peer that sent you this direct messagetarget: "<you>",// your channel peer's iddata: "<data>"// the data sent to you by <sender>}

Examples

Some example services built with Network Web Sockets:

Feedback

If you find any bugs or issues please report them on the Network Web Sockets Issue Tracker.

If you would like to contribute to this project please consider forking this repo, making your changes and then creating a new Pull Request back to the main code repository.

License

See the LICENSE file for more information.

Name		Name	Last commit message	Last commit date
_templates		_templates
examples		examples
lib		lib
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
channel.go		channel.go
client.go		client.go
client_server_test.go		client_server_test.go
discovery.go		discovery.go
peer.go		peer.go
proxy.go		proxy.go
service.go		service.go
templates.go		templates.go
transport.go		transport.go
utils.go		utils.go

Name		Name	Last commit message	Last commit date
_templates		_templates
examples		examples
lib		lib
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
channel.go		channel.go
client.go		client.go
client_server_test.go		client_server_test.go
discovery.go		discovery.go
peer.go		peer.go
proxy.go		proxy.go
service.go		service.go
templates.go		templates.go
transport.go		transport.go
utils.go		utils.go

Name		Name	Last commit message	Last commit date
_templates		_templates
examples		examples
lib		lib
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
channel.go		channel.go
client.go		client.go
client_server_test.go		client_server_test.go
discovery.go		discovery.go
peer.go		peer.go
proxy.go		proxy.go
service.go		service.go
templates.go		templates.go
transport.go		transport.go
utils.go		utils.go

Name		Name	Last commit message	Last commit date
_templates		_templates
examples		examples
lib		lib
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
channel.go		channel.go
client.go		client.go
client_server_test.go		client_server_test.go
discovery.go		discovery.go
peer.go		peer.go
proxy.go		proxy.go
service.go		service.go
templates.go		templates.go
transport.go		transport.go
utils.go		utils.go

Name		Name	Last commit message	Last commit date
_templates		_templates
examples		examples
lib		lib
.gitignore		.gitignore
LICENSE.txt		LICENSE.txt
README.md		README.md
channel.go		channel.go
client.go		client.go
client_server_test.go		client_server_test.go
discovery.go		discovery.go
peer.go		peer.go
proxy.go		proxy.go
service.go		service.go
templates.go		templates.go
transport.go		transport.go
utils.go		utils.go

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Getting started

Network Web Socket Interfaces

Local HTTP Test Console

JavaScript Interfaces

Web Socket Interfaces

Examples

Feedback

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Getting started

Network Web Socket Interfaces

Local HTTP Test Console

JavaScript Interfaces

Web Socket Interfaces

Examples

Feedback

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Network Web Sockets

Local Network broadcast channels with secure service discovery and encrypted proxy communication

Getting started

Network Web Socket Interfaces

Local HTTP Test Console

JavaScript Interfaces

Web Socket Interfaces

Examples

Feedback

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation