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

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

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master -  http://www.theagileschool.com/2012/03/scrummasters-checklist-roles.html • Product Owner • Feature Team The PDCA cycle ( http://www.theagileschool.com/2012/05/pdca-scrum-or-agile-why-is-it-important.html  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ http://www.scrum.org/Scrum-Guides will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I