liveBook · Manning

Session ID

A session ID is a value that associates multiple requests, activities, or interactions with a particular client, user, or application session.

How 3 Manning books explain it

Coding with AI

A session identifier is a value that uniquely identifies a user's active application session.

How it is used
Identifies and restores a user's active question session across browser requests.
How deep it goes
Traces cookie checks, creation, response setting, template display, and database retrieval, while stopping short of broader session-security treatment.
Examples
Uses a displayed session 42, Flask template variables, response.set_cookie, and a session-aware question-set query.
What you can do after
Operate/configure a Flask flow that creates, displays, stores, retrieves, and tests a session ID.

Read how Coding with AI explains session ID →

Build an AI Agent (From Scratch)

A session identifier is a value used to associate multiple agent invocations with the same persistent interaction session.

How it is used
Maintains conversation continuity across multiple agent.run() calls and supports resumable execution.
How deep it goes
Explains ID-based retrieval, context injection, event access, and saving, while deferring storage implementation beyond in-memory management.
Examples
Demonstrates Alice's remembered identity and a file-deletion approval resumed with the same session ID.
What you can do after
Build it from scratch by adding session_id handling, loading or creating sessions, injecting context, and saving completed state.

Read how Build an AI Agent (From Scratch) explains session ID →

Grokking Web Application Security

A session identifier is a value that links a client to a server-maintained or client-held web application session.

How it is used
Links repeated browser requests to an authenticated web session, typically through a cookie.
How deep it goes
Explains cookie transport and hijacking defenses, while deferring subdomain-cookie details.
Examples
Uses Set-Cookie and Cookie exchanges, a Secure; HttpOnly cookie, and a Wi-Fi interception demonstration.
What you can do after
Operate/configure it by enabling HTTPS, Secure and HttpOnly cookies, strong generated IDs, and URL-ID restrictions.

Read how Grokking Web Application Security explains session ID →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.