No agnosticism you’ve heard of Web Services, alike if you’re an ASP, PHP, Java, .NET or XML developer. If you haven’t, or don’t absolutely apperceive what they are, accept a attending at Kevin Yank’s “Web Services Demystified”.
Web Services are neither a fresh concept, nor a Microsoft creation. The abstraction has been about for a continued time — Netscape affected on the abstraction with their IIOP (Internet Inter-ORB Protocol) — and was discussed in an commodity by the cofounder of Netscape, Marc Andreessen, at the end of 1996.
In this commodity we’ll analyze how you can body and utilise your own Web Service.
Prerequisites
I’m bold that you accept a basal ability of .NET, Web forms, and accessing data. I’ll use an MS SQL Server database for this project, but you can additionally use Microsoft MSDE, which comes with the .NET Framework (if you charge advice award this, accept a attending at the SitePoint Forums), or adapt the cipher to assignment with an Access database through the OLEDB Namespace.
Usable Protocols
Because Web Services are advised to be as attainable as possible, one of the primary and best important aspects of the architectonics is to barter abstracts in a accustomed format. You can use three protocols to alteration abstracts in a .NET Web Service: Http-Get, Http-Post and SOAP (Simple Object Access Protocol). Let’s go over these protocols now. Because Http-Get and Http-Post are about the aforementioned thing, we’ll awning them together.
The Http-Get and Http-Post Protocols
Http-Get uses name/value pairs to canyon abstracts to and from a Web Service, and, as an HTTP-based protocol, it’s broadly accepted. You’ve apparently formed with afore if you’ve anytime acclimated the Request.QueryString() in ASP or ASP.NET. The Http-Get agreement appends a UUencoded cord to the end of a URL, which frequently appears like this:
www.e4ums.com/search.aspx?searchtext=search%
20for%20this&from=index.aspx