- It is easy to view table relationships, constraints, indexes, stored procedure in database but triggers are difficult to view and track.
- Triggers run on every update made to the table therefore it adds more load to the database and cause the system to run slow.
- Triggers execute invisible to client-application application so it is difficult to figure out what happens at the database layer.
- It is hard to follow their logic as it they can be fired before or after the database insert/update happens.
- Triggers run every time when the database fields are updated and it is overhead on system. It makes system run slower
- It is easy to forget about triggers and if there is no documentation it will be difficult to figure out for new developers for their existence.
If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler . The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension. For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: - It's just like a filter. The Modules are called before and after the handler executes . - HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional serv...
Comments
Post a Comment