Answer / sp

An ASP.NET HTTP handler is the process (frequently referred
to as the "endpoint") that runs in response to a request
made to an ASP.NET Web application. The most common handler
is an ASP.NET page handler that processes .aspx files. When
users request an .aspx file, the request is processed by
the page via the page handler.
To create a custom HTTP handler, you create a class that
implements the IHttpHandler interface to create a
synchronous handler or the IHttpAsyncHandler to create an
asynchronous handler. Both handler interfaces require you
to implement the IsReusable property and the ProcessRequest
method. The IsReusable property specifies whether the
IHttpHandlerFactory object (the object that actually calls
the appropriate handler) can place your handlers in a pool
and reuse them to increase performance, or whether it must
create new instances every time the handler is needed. The
ProcessRequest method is responsible for actually
processing the individual HTTP requests.

Answer / vikas kant

HTTP handlers are the .NET components that implement the
System.Web.IHttpHandler interface, they can act as a target
for the incoming HTTP requests and can be called directly
by using their file name in the URL.
HTTP handlers implement the following two methods:
1) ProcessRequest: called to process http requests and
2) IsReusable which indicates whether this instance of http
handler can be reused for fulfilling another requests of
the same type.

Answer / nitin

Actual flow is this Client made request -> Comes to IIS ->Forwarded to ASP.Net Engine (HTTP Mod and Hndlrs)-> Page made/processed at handler -> back to Modules ->back to IIS
-> request's response back to the client

These (Handlers) are the classes/Assemblies actually which comes in to picture after the client request has passed through the HTTP modules and now reached the Handlers.

What they does is this : to create the page in response to the client request and any custom operation that you wana perform on the request of the client before the page/request is dispatched off to the Modules Via IIS and then to the client as a response of the request. . . . .

Answer / a.mustaq ahmed

Whenever we to work with user defined File Extensions we go
for HTTP handlers.

Answer / rajeev kumar singh

Any Class that implements System.Web.IHttpHandler Interface becomes HttpHandler. And this class run as processes in response to a request made to the ASP.NET Site.

The most common handler is an ASP.NET page handler that processes .aspx files. When users request an .aspx file, the request is processed by the page through the page handler(The Class that implements System.Web.IHttpHandler Interface).

You can create your own custom HTTP handlers that render custom output to the browser.

Some ASP.NET default handlers are:
1) Page Handler (.aspx) – Handles Web pages
2) User Control Handler (.ascx) – Handles Web user control pages
3) Web Service Handler (.asmx) – Handles Web service pages
4) Trace Handler (trace.axd) – Handles trace functionality

Answer / swamy

HTTP handelers are process the requests at the endpoint in asp.net engine and renders the request to the client.

What are cao and sao.

0 Answers  

Explain the concept of MVC Scaffolding?

0 Answers   B-Ways TecnoSoft,

What is difference between datalist and gridview?

0 Answers  

About Global .asax ?

6 Answers   Satyam,

What are the page life cycle events?

0 Answers  

What is an asp.net web form?

0 Answers  

what is the differance between native code & managed code?

5 Answers   Microsoft,

which is better arraylist or dictionary?

2 Answers  

What is session authentication?

0 Answers  

Explain State management in asp.net

0 Answers   BirlaSoft,

Explain about the Class view window?

0 Answers  

1. What is the difference between Cache and Session? 2. I cache limited to page like viewstate or it's accessible through out the application like session? 3. Which one is better when I've some data that is to be used across the application? Why is to better than the other?

2 Answers   247Customer,