Chapter 4. Networking and Messaging
This chapter is mostly concerned with communication between Chrome App clients and servers on the Internet, using both APIs unique to Chrome Apps and APIs that are part of HTML5, such as WebSockets. I also discuss communication between windows in the same app as well as between apps on the same computer. We also explore notifications that an app can pop up at the top of the screen to alert the user.
The first section, which looks at the Socket API, is highly technical and perhaps not of interest to many readers, but it’s one of the most important Chrome APIs, so I cover it in detail. However, if you want to go directly to the APIs you’re likely to actually use, you can skip that section and start with The XMLHttpRequest API.
Socket API
The Internet communicates by using TCP/IP, the initials of its two most important protocols: Transmission Control Protocol and Internet Protocol. These were developed from research sponsored by the United States government that began in the 1960s. The TCP/IP standard was eventually adopted by the Department of Defense in 1982. A year or so later, an API implementing TCP/IP was released by the University of California in version 4.2BSD (Berkeley Software Distribution) of Unix, and that API came to be called BSD Sockets.
It’s not much of an exaggeration to call BSD Sockets the API of the Internet. Nearly all web servers, browsers, email systems, FTP clients and servers, and everything else that talks to the Internet is ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access