What exactly do you want the DLL to *DO* with the value? Pretty easy to
write a DLL that you can pass values to, if you don't care what happens to
them.
but citating approximatily Don Box "you must be insane to write ISAPI
filters"
Why? Because it's pure C without COM in mind and you wont have external
support for for instance unpacking the QueryStrings and cookies etc...
you'll have to write them yourself..
"Dionatan" <dion...@mixx.com.br> wrote in message
news:#We9ro4HAHA.283@cppssbbsa05...
Eggie,
there are indeed times where you MUST write filters and there's no other
option.
[Okay, this is NOT an advertisement just a fitting example:] Our newUrl
product encrypts any outbound URL and needs to decrypt that URL before it's
being picked up by ASP or CGI or any ISAPI extension. To do this, you need
to intercept any request at the earliest possible time, decrypt the Url and
replace the "Url" header the clear-text Url.
On the way out, we need to intercept all output from any CGI, ASP, ISAPI
(etc.) and detect/encrypt all Urls. Also, this can only be done using a
filter.
So, Don may be right that it doesn't support COM and that quite a lot of
manual work is required, but it's a truly useful mechanism for quite a few
problems.
However, for the question raised, an ISAPI __extension__ is what is
required, not a filter.
Regards
Clemens
--
Clemens F. Vasters, newtelligence AG
clem...@newtelligence.com
http://www.newtelligence.com
-----------------------------------------------------
Coaching,Training and Consulting
for SOAP, XML, COM(+)