Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / VB.NET / July 2007

Tip: Looking for answers? Try searching our database.

HttpWebRequest vs. web reference

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
cj - 30 Jul 2007 16:52 GMT
I'm trying to understand the difference between sites like Google that
offer web references (a .wsdl file) that I can add into my program and
those sites like USPS I have to create a HttpWebRequest to access.

Is the .wsdl file just a way to make it easier for us to user the
services of their sites in our programs?
dotNetDave - 30 Jul 2007 20:00 GMT
WSDL file is from a "true" web service. All services must have one and it
describes it's methods, paramaters and return types along with location of
the service.

The HttpWebRequest you are speaking about with UPS just means they don't
have true web services (don't get me started). Just a legacy application that
expects certian data and then returns data. Pain to use.

======================================
David McCarter [Microsoft VB.NET MVP]
www.vsdntips.com
VSDN Tips & Tricks .NET Coding Standards available at:
www.cafepress.com/vsdntips.20412485

> I'm trying to understand the difference between sites like Google that
> offer web references (a .wsdl file) that I can add into my program and
> those sites like USPS I have to create a HttpWebRequest to access.
>
> Is the .wsdl file just a way to make it easier for us to user the
> services of their sites in our programs?
Steven Cheng[MSFT] - 31 Jul 2007 08:23 GMT
Hi Cj,

As David has mentioned, a standard qualified XML webservice should has its
well defined WSDL document so that any client consumer can get the
service's interface and contract. Sure, there are some servcie providers
which doen't provide WSDL but provide a simple sample XML document(of the
SOAP REQUEST, RESPONSE) and the client-side can also consume it by manually
constructing such XML request and send it through some network
component(such as HttpWebRequest), however, this is surely not the
recommended approach.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
   

This posting is provided "AS IS" with no warranties, and confers no rights.
cj - 31 Jul 2007 15:20 GMT
Thanks David and Steven.

> Hi Cj,
>
[quoted text clipped - 15 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.