Skip to main content

ASP.net - Http handlers - Generic Hander

An HTTP Handler is a .NET class that executes whenever you make a request for a file at a certain path. Each type of resource that you can request from an ASP.NET application has a corresponding handler.

When you request an ASP.NET page, the Page class executes. The Page class is actually an HTTP Handler because it implements the IHttpHandler interface. Other examples of HTTP Handlers are the TraceHandler class, which displays applicationlevel trace information when you request the Trace.axd page and the ForbiddenHandler class, which displays an Access Forbidden message when you attempt to request source code files from the browser.

Similarly you can create your own HTTP handlers for acting on any requests received at webserver.

Generic Hander

Add a generic handler by right clicking on the project explorer > Add> new item> select Generic Handler.

A new file with ASHX extension is created.


Here is a sample code which I got from Steven Walthers book. This handler creates image dynamically based on the QueryString value received

[WebService(Namespace = "http://tempuri.org/")]
    [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
    public class ImageTextHandler : IHttpHandler
    {

        public void ProcessRequest(HttpContext context)
        {
            // Get parameters from querystring
            string text = context.Request.QueryString["text"];
            string font = context.Request.QueryString["font"];
            string size = context.Request.QueryString["size"];

            Font fntText = new Font(font, float.Parse(size));

            Bitmap bmp = new Bitmap(10, 10);
            Graphics g = Graphics.FromImage(bmp);

            SizeF bmpsize = g.MeasureString(text, fntText);
            int width =(int) Math.Ceiling(bmpsize.Width);
            int height = (int)Math.Ceiling(bmpSize.Height);
            bmp = new Bitmap(bmp, width, height);
            g.Dispose();

            // Draw the text
            g = Graphics.FromImage(bmp);
            g.Clear(Color.White);
            g.DrawString(text, fntText, Brushes.Black, new PointF(0, 0));
            g.Dispose();

            // Save bitmap to output stream
            bmp.Save(context.Response.OutputStream, ImageFormat.Gif);

        }

        public bool IsReusable
        {
            get
            {
                return true;
            }
        }
    }

ProcessRequest() method is responsible for outputting any content that the handler renders to the browser.


The handler also includes an IsReusable property. The IsReusable property indicates whether the same handler can be reused over multiple requests. You can improve your application’s performance by returning the value True. Because the handler isn’t maintaining any state information, there is nothing wrong with releasing it back into the pool so that it can be used with a future request.


How can I use this generic handler?

You can put the following code in any ASPX file

<img src="ImageTextHandler.ashx?text=Hello World&font=WebDings&size=20" />
<br />
<img src="ImageTextHandler.ashx?text=Hello World&font=Comic Sans MS&size=20" />
<br />
<img src="ImageTextHandler.ashx?text=Hello World&font=Courier New&size=20" />


You will get a browser output like the following
The basic idea here is not to show how to create a image file on the fly but the handling of request by ASHX file


Comments

Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed. Plan  This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team. DO Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process. Check Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down. ACT If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

Why is potentially shippable product quality important

Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified