ASP.NET handles all the communications protocol requests returning from the user and generates the acceptable response for it. ASP.NET framework is aware of the way to method totally different reasonably requests supported extension, as an example, It will handle request for .aspx, .ascx and .txt files, etc. once it receives any request, it checks the extension to envision if it will handle that request and performs some predefined steps to serve that request.
Now as a developer, we would wish to own a number of our own practicality obstructed in. we would wish to handle some new reasonably requests or maybe we wish to handle associate existing request ourselves to own additional management on the generated response, as an example, we have a tendency to might want to choose however the request for .jpg or .gif files are going to be handled. Here, we'll want associate HTTPHandler to own our practicality in situ.
There ar|are} some situations wherever we have a tendency to are happy with the method ASP.NET is handling the requests however we wish to perform some further tasks on every request, i.e., we wish to own our tasks execute along side the predefined steps ASP.NET is taking over every request. If we wish to try and do this, we are able to have HTTPModule in situ to realize that.
So from the on top of discussion, it's clear that HTTPHandlers square measure utilized by ASP.NET to handle the particular requests supported extensions. HTTPModule, on the opposite hand, is employed if we wish to own our own practicality operating along side the default ASP.NET practicality. there's one Handler for a selected request however there may be N range of modules for that.
Now as a developer, we would wish to own a number of our own practicality obstructed in. we would wish to handle some new reasonably requests or maybe we wish to handle associate existing request ourselves to own additional management on the generated response, as an example, we have a tendency to might want to choose however the request for .jpg or .gif files are going to be handled. Here, we'll want associate HTTPHandler to own our practicality in situ.
There ar|are} some situations wherever we have a tendency to are happy with the method ASP.NET is handling the requests however we wish to perform some further tasks on every request, i.e., we wish to own our tasks execute along side the predefined steps ASP.NET is taking over every request. If we wish to try and do this, we are able to have HTTPModule in situ to realize that.
So from the on top of discussion, it's clear that HTTPHandlers square measure utilized by ASP.NET to handle the particular requests supported extensions. HTTPModule, on the opposite hand, is employed if we wish to own our own practicality operating along side the default ASP.NET practicality. there's one Handler for a selected request however there may be N range of modules for that.
0 comments:
Post a Comment