Re: HTTP handlers/Modules vs ISAPI dlls
From: Scott Allen (bitmask_at_[nospam)
Date: 08/23/04
- Next message: Scott Allen: "Re: debug in real time"
- Previous message: Karl: "Re: HTTP handlers/Modules vs ISAPI dlls"
- In reply to: Norton: "HTTP handlers/Modules vs ISAPI dlls"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 22 Aug 2004 21:47:29 -0400
Speaking *generally*:
I can write an ISAPI filter in C++ that is more performant than a C#
module implementing the same functionality. This would be because the
filter is written in C++.
Also speaking generally:
The C++ version would take 4x as long, would have 4x the number of
bugs, and have 4x the number of security holes. Just memory management
alone in a non-trivial ISAPI filer required very careful attention to
detail.
A handler written in managed code is the answer to an ISAPI dll. There
are so many benefits to managed code I'd never consider doing it in
C++ again.
-- Scott http://www.OdeToCode.com On Sun, 22 Aug 2004 20:46:21 -0400, "Norton" <thenortonz@hotmail.com> wrote: >I had a person tell me the other day that a person would not be able to beat >the efficiency of an ISAPI dll, especially by using handlers/modules. Of >course, they could only say the reason was that it is written in C++, which >should have nothing to do with it. > >But, in general, can you write a handler that will handle just as many >connections as an ISAPI dll? Isn't a handler a managed code answer to the >ISAPI dll solution? > >Thanks. > >Norton. >
- Next message: Scott Allen: "Re: debug in real time"
- Previous message: Karl: "Re: HTTP handlers/Modules vs ISAPI dlls"
- In reply to: Norton: "HTTP handlers/Modules vs ISAPI dlls"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|