WSE3 Transport Independence On Consumer-Side

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: "Mork" <danmork@xxxxxxxxx>
Date: 14 Jun 2005 09:45:20 -0700

It appears in WSE3 that you can take your ASMX Web service
(System.Web.Services.WebService subclass) and host it outside of IIS
and call it over TCP/IP. To achieve transport independence on the
consumer-side, however, you're still going to need a class deriving
from SoapClient, right? (since WebServicesClientProtocol classes derive
from SoapHttpClientProtocol)

So, if you know you're using WSE, what's the benefit of using the
IDE-generated WebServicesClientProtocol subclass over using a
WSEWSDL3.EXE-generated SoapClient subclass?

Cheers,
~Mork

.

Follow-Ups:
- Re: WSE3 Transport Independence On Consumer-Side
  - From: Mork

Prev by Date: RE: WSE and SSL
Next by Date: RE: filters in WSE3.0
Previous by thread: WSE 3.0 and SecureConversation
Next by thread: Re: WSE3 Transport Independence On Consumer-Side
Index(es):
- Date
- Thread