Tous les livres

Professionnel

Applis À propos Coach Connexion Commencer la lecture

Quantitative Finance · Glossaire

Qu'est-ce que « REST interface, persistent connection, connection pool » ?

Aussi appelé : REST interface · persistent connection · connection pool

Definition 17.1 Low-Latency Software · Chapitre 17 — WebSocket, REST, TLS and JSON at Speed

A REST interface exposes a service as resources addressed by URLs and manipulated by HTTP requests (GET to read, POST to create, DELETE to remove), each request carrying everything the server needs to process it. A persistent connection carries many HTTP requests and responses over one TCP (and TLS) connection instead of opening one per request. A connection pool keeps a set of open persistent connections to a server and lends an idle one to each request.

A WebSocket connection over TLS 1.3: one round trip for TCP, one for TLS, one for the HTTP upgrade; then each message is a WebSocket frame inside a TLS record. A REST order on a new connection pays the first two round trips; on a persistent connection, none.
Figure 17.1. A WebSocket connection over TLS 1.3: one round trip for TCP, one for TLS, one for the HTTP upgrade; then each message is a WebSocket frame inside a TLS record. A REST order on a new connection pays the first two round trips; on a persistent connection, none.
Lire dans le chapitre →