9.1 TRACING THE PATH OF A REQUEST—A DIFFERENT VIEW
Recall the diagram explained in the first section on Web Essentials, where a typical HTTP request is traced out. Imagine the same scenario, but with a different conceptual view where it is split into two areas—the client which acts as a requestor and the service which acts as the resource. This way, the resource can cater to any number of such requests as long as they all follow a certain set of conventions and standardized interface while communicating between server and the client.
The path that is traced is shown in the Figure 9.1. Removing the shaded blocks, it is actually the same figure appearing in the section on Web Essentials (Figure 2.8). Conceptually imagine that the two shaded portions ...
Get Web Technology: Theory and Practice now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
