ATL Server and IIS

[Javier Estrada]

Is there a way to get rid of IIS and only use the ATL
Server framework? That is, can I write my own transport to
feed an ATL Server project without depending on IIS?

I've seen an article and some code that claims that the
transport can be rewritten, but I do not understand whether
that means getting rid of IIS altoghther.

Can anyone clarify?

Regards,

Javier

 

[Bogdan Crivat [MSFT]]

It depends on what you want to do.
The ATL Server framework can be used outside of IIS to process requests,
either SOAP or regular HTTP requests.

ATL Server applications are ISAPI extensions. They have well defined entry
points (see the ISAPI specification) and can,
therefore, be loaded by any process that invokes the exported methods and
provides the necessary input parameters.
The process will be responsible to dispatch various requests to the specific
ATL Server ISAPI DLLs.

The HTTP transport for SOAP can be changed to run outside of IIS (the SOAP
Transport sample in MSDN shows how to do this, it does not use IIS at all).
The sample code will work for a small application, with a reduced traffic.
Most likely, it will take a lot of work to develop an alternate transport
that has the same scalability and security features as IIS.


--
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. It is for newsgroup
purposes only.

thanks,
bogdan

 

[Javier Estrada]

Bogdan,

First of all, thx. It was actually your article that I read and I had the
same impressions that you describe in your response. I fired up a question
to our Premier Support representative and the answer was that it was tied up
to IIS (should have asked them to ask you ;-).

We're using White Mesa SOAP Server (WMSS) with our web service. Our needs
are small and it meets the requirements for our customers and what the
company wants to use for now, therefore, we disregarded IIS--long discussion
but it was decided that way. In addition, we use SOAP 1.1 using a
document-style payload (no WSDL, mainly has to do with our target audience
experience with SOAP and Web Services. We had to go simple).

We have used WMSS for release 1.0 of our web service, but I wanted to
eliminate it if possible--one less thing in the food chain, in case of
failures. From what I understand, I could follow these options if I wanted
to use ATL Server:

1. Use WMSS and transform the inputs to IIS inputs, or,
2. Replace the HTTP transport.

Our application does not have too much traffic, and actually it can work
with only one customer at a time (blocking, or synchronous operations. I'll
explore my options.

Regards,

Javier