"The advantage of using the generic handler is twofold.
First, it's usually much more convenient to generate a simple handler than it is
to create a whole new assembly to handle the request. Second, you don't
need to run interference with either Web.Config or with IIS. That is, Web.Config and IIS
already understand what to do about files with the extension of .ashx"
"SQLAjax" web application: Less code on the web server...More-scalable...Easier
to maintain:
Why do we use highly-scalable database application platforms like SQL Server, Oracle,
and DB2 as data storage engines, but not take advantage of their performance and
scalability power for our "business logic" code? Why can't AJAX code simply pass XML or JSON messages to databases through
simple HTTP handlers like .NET .ashx files? Object-oriented approaches like SOAP
and ORM tightly-bind
data and UI code between the browser and the web, and therefore are often the exact
opposite of what
service-oriented architectureis
all about.
"When used in massive quantities, Ajax applications can clog up network
traffic. A more important concern, in turn, is that the large amount of traffic
exposes Ajax applications to Web services vulnerabilities. When these vulnerabilities
are exploited, the
system or applications will perform poorly."
--
http://www.ibm.com/developerworks/web/library/wa-aj-speed.html
