Book Image

Learn ECMAScript - Second Edition

By : MEHUL MOHAN, Narayan Prusty
Book Image

Learn ECMAScript - Second Edition

By: MEHUL MOHAN, Narayan Prusty

Overview of this book

Learn ECMAScript explores implementation of the latest ECMAScript features to add to your developer toolbox, helping you to progress to an advanced level. Learn to add 1 to a variable andsafely access shared memory data within multiple threads to avoid race conditions. You’ll start the book by building on your existing knowledge of JavaScript, covering performing arithmetic operations, using arrow functions and dealing with closures. Next, you will grasp the most commonly used ECMAScript skills such as reflection, proxies, and classes. Furthermore, you’ll learn modularizing the JS code base, implementing JS on the web and how the modern HTML5 + JS APIs provide power to developers on the web. Finally, you will learn the deeper parts of the language, which include making JavaScript multithreaded with dedicated and shared web workers, memory management, shared memory, and atomics. It doesn’t end here; this book is 100% compatible with ES.Next. By the end of this book, you'll have fully mastered all the features of ECMAScript!
Table of Contents (18 chapters)
Title Page
PacktPub.com
Contributors
Preface
Index

HyperText Transfer Protocol (HTTP)


HTTP is a stateless protocol. A stateless protocol means that there is no state being stored on the server, which, in turn, means that the server forgets everything once it has sent a response to the client. Consider the following situation:

You've typed http://example.com in your browser. When your request hits the server, the server is aware of your IP address, your requested page, and any other headers associated with your HTTP request. It fetches the content from the filesystem or database, sends the response to you, and then forgets about it.

Upon every new HTTP request, the client and server interact as if they're meeting for the first time. So, doesn't that mean our earlier Facebook example is true in the real world as well?

Essentially, that is the case. All websites use cookies for authentication purposes, which is a way to fake the statefulness of a protocol. Remove cookies from every request and you will be able to see the raw, stateless HTTP protocol...