Handler
A handler is a callable or software component that processes an event, request, message, or other input and performs associated processing.
ASP.NET Core in Action, 3e
A handler is an application component that receives a framework-dispatched request or event and performs the corresponding processing.
- How it is used
- Coordinates processing after routing selects an HTTP endpoint or Razor Page.
- How deep it goes
- Works through handler forms, selection conventions, binding, delegation, validation, and response choices in small applications.
- Examples
- Uses a fruit CRUD API, a to-do category page, a search page with multiple handlers, and a checkout form.
- What you can do after
- Build it from scratch by mapping minimal API handlers or writing Razor Page methods that delegate work and select responses.
React Quickly, Second Edition
Event handling is the process of responding to events generated by user interactions or changes in a web document.
- How it is used
- Connects user interactions and browser events to React UI updates through handlers assigned to JSX elements.
- How deep it goes
- Works through handler definitions, event objects, propagation, default actions, and manual listener cleanup, with capture handlers flagged as uncommon.
- Examples
- Uses counters, a video player, a contact form, a login form, a window-size display, and an expandable menu.
- What you can do after
- Build it from scratch: attach JSX handlers for interactions and add cleaned-up native listeners when React cannot manage the target or event.
Learn Go with Pocket-Sized Projects
An HTTP handler is a function or component that receives an HTTP request and produces an HTTP response.
- How it is used
- Routes web-service requests to endpoint logic that fills an HTTP response.
- How deep it goes
- Works through registration, method checks, response ordering, JSON bodies, and direct tests; does not descend into server internals.
- Examples
- Uses a POST /games handler, curl responses, a JSON guess request, and a recorder-based handler test.
- What you can do after
- Build it from scratch: register a Go endpoint handler, produce its response, and test it directly.
Read how Learn Go with Pocket-Sized Projects explains handler →
Pro ASP.NET Core 7, Tenth Edition
A callable operation that responds to an occurrence such as a user interaction or program event.
- How it is used
- Handles Razor Page HTTP requests and Blazor component events through methods selected by request conventions or event attributes.
- How deep it goes
- Works through handler naming, selection, parameter binding, redirects, and server-side event dispatch; defers detailed model binding to another treatment.
- Examples
- Uses a cart add/remove flow, a product-price editor, and Blazor counter buttons to show handlers in action.
- What you can do after
- Build it from scratch: implement GET, POST, and named Razor Page handlers, then wire a Blazor button to a component method.
Read how Pro ASP.NET Core 7, Tenth Edition explains handler →
Build a Frontend Web Framework (From Scratch)
A programmatic callback that responds to an event raised by a user interface or other software component.
- How it is used
- Connects browser interactions, dispatched commands, and component events to functions that respond or update application state.
- How deep it goes
- Builds registration and dispatch, then elaborates component binding, argument forwarding, and unsubscription rather than stopping at a callback definition.
- Examples
- Uses to-do input and button listeners, a remove-todo command, and parent-supplied handlers for child events.
- What you can do after
- Build it from scratch: register DOM and command handlers, bind component context, and unsubscribe component event handlers on unmount.
Read how Build a Frontend Web Framework (From Scratch) explains handler →
D3.js in Action, Third Edition
An event listener is a callback registration that runs code in response to a specified event on an interface object.
- How it is used
- Connects user input and screen changes to interactive chart updates, filters, tooltips, and responsive layouts.
- How deep it goes
- Defines D3 .on() callbacks, event objects, bound data, and concrete click, hover, and resize implementations.
- Examples
- Uses histogram filter buttons, temperature-chart circles, responsive text labels, SVG grids, and circle-pack language nodes.
- What you can do after
- Apply it via D3 selections or JavaScript window events to update chart state, tooltips, and responsive dimensions.
Web Components in Action
An event listener is a callback registration that causes code to run when a specified event occurs on an object.
- How it is used
- Connects browser events such as clicks and mouse movement to component behavior.
- How deep it goes
- Demonstrates listener registration, callback scope, and event-driven component behavior without surveying the event API.
- Examples
- Uses photo-carousel buttons, a draggable slider, and mouse-strummed harp strings as concrete event-driven examples.
- What you can do after
- Apply it via addEventListener to route click or mouse events into component methods.
Refactoring to Rust
An NGINX HTTP handler is a module function that receives an NGINX request structure and returns an integer request-processing status.
- How it is used
- Routes calculator POST requests through an NGINX dynamic module toward a Rust HTTP interface.
- How deep it goes
- Explains FFI signatures, body-loading callbacks, pointer checks, and UTF-8 conversion; the illustrated handler stops at logging the body.
- Examples
- Shows calculator POST commands, a C handler declaration, Rust callback code, and request-buffer extraction.
- What you can do after
- Apply it via NGINX’s C module API and Rust FFI to load and inspect POST request bodies.
Spring in Action, Sixth Edition
A Spring Integration handler contract for processing an incoming message.
- How it is used
- Handles messages from integration channels, either performing service work or ending an email-to-order flow.
- How deep it goes
- Works through lambda and class implementations, channels, headers, and return values without examining framework internals.
- Examples
- Demonstrates payload logging, repository-backed order saving, and posting email-derived orders to an API.
- What you can do after
- Apply it via @ServiceActivator or IntegrationFlows.handle() to process a message and optionally forward a result.
Go by Example
A handler is a software component that receives an operation or request and produces the corresponding processing result.
- How it is used
- Processes HTTP requests into responses for service endpoints, health checks, and routed API operations.
- How deep it goes
- Explains function adaptation, closures, status responses, routing, and direct tests, while deferring middleware composition.
- Examples
- Uses an OK health endpoint, a URL-shortening POST handler, ServeMux routes, and a ResponseRecorder-based test.
- What you can do after
- Apply it via Go’s net/http and httptest packages to register, test, and compose request handlers with explicit dependencies.
Learn Docker in a Month of Lunches, Second Edition
A message handler is a software component that receives messages or events and performs processing in response.
- How it is used
- Processes queued events after publishers hand them off, keeping event-driven work outside the user-facing request.
- How deep it goes
- Explains subscriptions, buffering, scaling, and asynchronous effects, while using existing handler images rather than detailing handler internals.
- Examples
- Uses to-do item saving, audit logging, Elasticsearch indexing, calendar reminders, and a text-mutating handler.
- What you can do after
- Operate and configure handlers with Docker Compose, including scaling a handler group and adding an audit subscriber.
Read how Learn Docker in a Month of Lunches, Second Edition explains handler →
Machine Learning System Design
A software component that receives and processes requests made through an API.
- How it is used
- Routes API requests to underlying services and returns structured responses, serving as the interface between callers and backend functionality.
- How deep it goes
- Explains request parsing, delegation, JSON response wrapping, and error handling, while explicitly excluding business logic.
- Examples
- Uses a photo-search endpoint with optional filters and a JSON response of photo IDs and relevance scores.
- What you can do after
- Build it from scratch by parsing requests, delegating work, formatting JSON responses, and handling errors.
Python How-To
A handler is a logging component that processes records emitted by a logger, typically by writing them to a destination.
- How it is used
- Routes application event records to persistent files, interactive consoles, or other destinations.
- How deep it goes
- Demonstrates attaching handlers, using multiple destinations, and setting per-handler levels, while leaving less common handler types largely unexplored.
- Examples
- Uses task-removal records, console output, duplicate file handlers, and files filtered at WARNING and CRITICAL levels.
- What you can do after
- Apply Python’s logging module to route records to files or consoles and filter them with handler levels.
Build AI-Enhanced Web Apps
Event handling is the processing of user or system events by executing associated application logic.
- How it is used
- Routes API requests to backend logic or hooks into LangChain.js execution stages for logging, monitoring, and error handling.
- How deep it goes
- Specifies route placement, HTTP method exports, request handling, and caching, and maps callback events to methods.
- Examples
- Uses a Next.js POST route that reads JSON and returns a response, plus callback methods for chain and LLM events.
- What you can do after
- Apply Next.js route conventions to handle API requests or LangChain.js callbacks to trace execution and errors.
Functional Design and Architecture: Examples in Haskell
A Handler is the Servant monad and request-handler type for implementing web operations and producing HTTP responses.
- How it is used
- Connects Servant HTTP routes to request-processing functions that return responses and translate failures into HTTP errors.
- How deep it goes
- Defines Handler, demonstrates database-backed handlers, and extends them with ReaderT runtime execution; it stops short of Servant internals.
- Examples
- Uses AstroAPI routes, object retrieval, database queries, method-handler signatures, and handler composition with :<|>.
- What you can do after
- Apply it via Servant to implement typed HTTP endpoints and delegate domain scenarios through a runtime-aware handler layer.
Read how Functional Design and Architecture: Examples in Haskell explains handler →
Java Persistence with Spring Data and Hibernate epub
An event handler is a component that receives an event and performs processing in response to it.
- How it is used
- Adds authorization, auditing, tenant assignment, or other side effects to persistence and repository lifecycle events.
- How deep it goes
- Compares JPA callbacks, Hibernate interceptors, core event listeners, and repository handlers, including configuration and singleton-like lifecycle constraints.
- Examples
- Uses authorization during entity loading, audit-log side effects, tenant assignment, and REST create, save, delete, and link events.
- What you can do after
- Apply it via JPA, Hibernate, or Spring Data REST extension points to execute custom logic around supported lifecycle events.
Read how Java Persistence with Spring Data and Hibernate epub explains handler →
Get Programming: Learn to code with Python
An event handler is a function or code unit that runs in response to an interaction or other event generated by a user-interface component.
- How it is used
- Uses functions to give GUI widgets behaviors such as responding to clicks, menu selections, and keypresses.
- How deep it goes
- Explains definition, widget linkage, input reading, interface updates, and modular dispatch, but not event-system internals.
- Examples
- Demonstrates a button changing a window color, a countdown timer, and a two-player canvas game controlled by keypresses.
- What you can do after
- Build it from scratch by connecting tkinter widgets and canvas events to functions that update a GUI.
Read how Get Programming: Learn to code with Python explains handler →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
An HTTP route handler is a server-side function that processes requests matching a specified HTTP route and produces a response.
- How it is used
- Defines server behavior for matching HTTP routes, from returning a simple response to streaming media or receiving service messages.
- How deep it goes
- Builds handlers as Express callbacks using request and response objects, including async work, but leaves Node.js streaming internals unexplored.
- Examples
- Uses a Hello World GET route, a video-file stream, and a POST route that records a viewed video path.
- What you can do after
- Apply via Express by defining route callbacks that return responses, stream files, or process POST request bodies.
Secrets of the JavaScript Ninja, Second Edition
A callable routine that runs in response to a dispatched event.
- How it is used
- Adds interactivity by running code in response to browser events.
- How deep it goes
- Explains registration, event data, and serial queue execution, while deferring event propagation details.
- Examples
- Uses mousemove and click callbacks that append messages, plus a button click handler.
- What you can do after
- Apply it via addEventListener to respond to clicks and inspect the event object.
Read how Secrets of the JavaScript Ninja, Second Edition explains handler →
Akka in Action, Second Edition
An event handler is a function that applies a persisted event to an actor's state during normal processing or recovery replay.
- How it is used
- Rebuilds actor state from persisted events inside EventSourcedBehavior.
- How deep it goes
- Defines the function signature and role, but does not show event-specific update logic.
- Examples
- Uses a cargo-container state and CargoAdded event to illustrate persisted state transitions.
- What you can do after
- Builds an event-sourced actor by supplying an eventHandler alongside persistence ID, state, and commandHandler.
.NET MAUI in Action
An event handler is a method that executes in response to an event raised by a software component.
- How it is used
- Connects a .NET MAUI button click to permission checks, location retrieval, and sharing behavior.
- How deep it goes
- Demonstrates a worked event flow with asynchronous calls and conditional permission handling.
- Examples
- Uses the FindMe button, OnFindMeClicked, ShareLocation, UsernameEntry, and a shared Bing Maps location link.
- What you can do after
- Apply it via .NET MAUI by wiring a button event to an asynchronous C# method.
Grokking Concurrency
An event handler is a function or component that processes an event from a particular source or event type.
- How it is used
- Processes requests tied to a particular event source or event type within event-based concurrency.
- How deep it goes
- Defines handlers as callbacks and identifies three socket-related roles, without detailing their implementations.
- Examples
- Uses _on_accept, _on_read, and _on_write for connection acceptance, client messages, and client writes.
- What you can do after
- Understand how to associate callbacks with specific events and sources.
Related concepts
- event handlingused by · Event handling is the process of receiving events and invoking associated code to respond to them.
- methodused by · A method is a callable operation associated with an object or type and invoked through that association.
- business logicuses · Business logic is the domain-specific rules, computations, and decisions that determine how a software system behaves and processes operations.
- routinguses · Routing is the selection of a path, destination, or processing component to direct an item, request, or flow toward an intended endpoint.
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.