I’ve been developing ASP.NET applications since 2002. Up until recently, I’d overlooked a pretty useful part of the ASP.NET Framework : Generic Handlers.
Generic Handlers are basically HTTP Handlers that can process requests to exactly one url (Http Handlers are classes that need to be registered in the web.config for what urls they run on, and often manipulate requests/responses that go to/come from .aspx pages). They are “closer to the wire” than .ASPX WebForms or .ASMX WebServices. They are built with only two requirements, implement:
public void ProcessRequest(HttpContext context);
(this contains the logic for when this page is requested) and, implement:
public bool IsReusable;
(this tells ASP.NET whether it can use one instance to serve multiple requests).
Generic Handlers are similar to web forms – they are reachable by a standard get/post to the url they are located in. ASP.NET starts you off with context object (passed into the ProcessRequest() function you implement), which you then use to communicate with the request (form and query vals, etc) and the response object (to write info to the browser). You can decide in what capacity you want that context to have access to the session:read/write, readonly, or none. Unlike web forms, generic handlers skip some of the niceties: the designer/xaml/servercontrol model, themes, viewstate, etc. Thus, generic handlers can be much more efficient for many tasks that make no use of those features.
Here’s a few common tasks where a generic handler would be more suitable than a web form:
- Writing out the contents of files stored in the db/elsewhere for download
- Writing out manipulated images, generated graphics, etc
- Writing out generated PDFs/CSVs etc
- Writing out data without the webservice overhead
- xml for other systems or sites
- html for simple AJAX get requests to replace page content
- JSON for more advanced ajax data communication
- Callback urls for data sent from other sites through a http post
- Building a “REST API”
- A url that outputs status info about the website, for use by a content switch or other monitoring system
- Writing out dynamic JS/CSS based on server variables, browser capabilities, etc
Basically, anywhere I found myself before creating an ASPX page, but clearing everything on the .ASPX and using Response.Write()/Response.BinaryWrite() to talk to the browser or another system from the code behind, I should have been using a .ASHX handler instead and saving my webserver some work.
Here is a sample GenericHandler to get you started. It writes out a simple js file that gives you some useful globals you can use in other js files. Its meant to just be an example of the types of things you can do with generic handlers, and doesn’t necessarily produce what you might want in your own dynamic JS file.