>>Out of the 10 or 12 times i've needed to expose a service over the web, SOAP turned out to be the best solution only twice.
>
>If you don't mind sharing, what were the two and why did they stand apart?
>

They were applications that exposed the same components both over the web and locally. A single component handled both COM and SOAP traffic. SOAP worked great because I didn't have to reengineer an interface just to expose something over the web; the SOAP toolkit built the web interface for me.