[Fwd: [wsf-c-dev] Re: axis2 module for IIS - General Ideas]

[supun]

These are my thoughts about using the http.sys for writing the IIS module.

1. If we are going to use the HTTP api (Http.sys) directly, the module 
will be a standalone application similar to the simple http server. So I 
don't think it is an option.
   What http.sys provides us is a handler for a http request que. We 
listen for this que for requests and when a request arrives, process the 
request as in a noraml web server.
   So ultimately ultimately our application will be a another web server.
2. II6 uses the http.sys internally. So if we write our module for II6 
the advantage of http.sys will be available to us automatically. The way 
to write a module
   for II6 is to write an ISAPI extention. I  couldn't find any other 
way to this.

Supun

Samisa Abeysinghe wrote:
> I have done some reading about how to create a module to intergrate 
> axis2c with IIS.
> There are two ways to extend the IIS capability.
>
>               1. ISAPI filters
>               2. ISAPI extensions

I would recommend not using either of these, but building on http.sys
directly.  See for example:

http://dotnetjunkies.com/Tutorial/99DD7042-532D-4DB4-8625-1CD8BF422D64.dcik
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a2a45c42-38bc-464c-a097-d7a202092a54.mspx?mfr=true 

http://msdn2.microsoft.com/en-us/library/ms191310.aspx

This requires IIS 6.0 and at least Windows Server 2003 or Windows XP
SP2, but it's definitely the way of the future, and provides potentially
much better performance than ISAPI filters or extensions.

James





_______________________________________________
Wsf-c-dev mailing list
Wsf-c-dev at wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev