Actually web services do not necessarily need to go through IIS and HTTP.
They can be configured to use local resources in a more direct manner.
Still, there is a tiny amount of overhead so your primary point is still
valid even though it has been significantly diminished.
Some people might consider this tiny amount of overhead to be worth it in
order to have a more reusable service-oriented architecture. But that
mostly comes down to opinion and how you envision your object model
potentially evolving over the long term.

Signature
I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net
> for the web service you need a connection to your IIS all the time. For a
> class just reference the class then call the methods in that. You can
[quoted text clipped - 13 lines]
>>
>> What are the trade offs for using each?
Actually web services do not necessarily need to go through IIS and HTTP.
interesting. How would that work? Everything I've seen, read, and even
taught in class stated a web service has run via a web server. How can you
use or access a web service any other way?
> Actually web services do not necessarily need to go through IIS and HTTP.
> They can be configured to use local resources in a more direct manner.
[quoted text clipped - 23 lines]
>>>
>>> What are the trade offs for using each?
ThatsIT.net.au - 07 Jun 2007 17:13 GMT
> Actually web services do not necessarily need to go through IIS and HTTP.
> interesting. How would that work? Everything I've seen, read, and even
> taught in class stated a web service has run via a web server. How can
> you use or access a web service any other way?
I have read that they can be passed though many protocols but have never
done so.
I use web services because I always think that I may need to reuse them but
often don't and then think a class may of been the better choice.
I can consume web services in WSH excel asp pages and HTA's
can I do that with classes? If so how do I reference them?
I also remember trying to use optional parameters in a WS and they are not
allowed.
I also assume that you can not have abstract WS's
>> Actually web services do not necessarily need to go through IIS and HTTP.
>> They can be configured to use local resources in a more direct manner.
[quoted text clipped - 23 lines]
>>>>
>>>> What are the trade offs for using each?
Steve C. Orr [MCSD, MVP, CSM, ASP Insider] - 07 Jun 2007 23:23 GMT
Here's the information you requested that details how you can use protocols
other than HTTP with web services:
http://www.code-magazine.com/Article.aspx?quickid=0611051

Signature
I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net
> Actually web services do not necessarily need to go through IIS and HTTP.
> interesting. How would that work? Everything I've seen, read, and even
[quoted text clipped - 28 lines]
>>>>
>>>> What are the trade offs for using each?