One round trip, three dependent calls
This page authenticates a user, then fetches that user's profile and notifications, both of which need the user ID from the first call. Pipelined, all three travel in a single HTTP request. Done the ordinary way, they take three. Only the round trips differ; the server does identical work either way.
Pipelined
One session, calls chained on unresolved promises.
HTTP round trips…
Elapsed…
Not run yet.
Sequential
A fresh session per call, each awaited in turn.
HTTP round trips…
Elapsed…
Not run yet.