Important:
Chrome will be removing support for Chrome Apps on Windows, Mac, and
Linux. Chrome OS will continue to support Chrome Apps. Additionally,
Chrome and the Web Store will continue to support extensions on all
platforms.
Read the announcement and learn more about
migrating your app.

Network Communications

Chrome Apps can act as a network client
for TCP and UDP connections.
This doc shows you how to use TCP and UDP
to send and receive data over the network.
For more information,
see the
Sockets UDP,
Sockets TCP and
Sockets TCP Server APIs.

Note: The previous version of the networking APIs (socket) has been
deprecated.

API Samples:
Want to play with the code?
Check out the
telnet
and udp samples.

Manifest requirements

For Chrome Apps that use TCP or UDP,
add the sockets entry to the manifest
and specify the IP end point permission rules.
For example:

When a new connection is established, onAccept is invoked with
the clientSocketId of the new TCP connection. The client socket ID
must be used with the sockets.tcp API.
The socket of the new connection is paused by default. Un-pause it with
sockets.tcp.setPaused to start receiving data.