One of the many benefits of object-oriented programming is that it allows for reuse of logic. For example, classes can be created that contain a base level of functionality.
As we've discussed in the previous installments of this article series, Web services are comprised of a number of core standards, including:
About a year ago I wrote an article titled, Syndicating Your Web Site's Content with RSS.
As we discussed in Part 1 of this article series, a Web service is invoked with a client sending a SOAP-formatted message to the server where the Web service resides. The server then:
In Part 1 of this article series we looked at the pieces involved in using Web services, including SOAP, which is the standard by which the messages passed to and from a Web service are encoded by.
Welcome to the 5th installment of an Extensive Examination of Web Services. In Part 1 we examined the basics of Web services, looking at what, precisely, standards made up Web services.
So far in this article series we have examined the standards involved in Web services, looked at creating Web services with Visual Studio .NET, and have examined WSDL and creating proxy classes to consume a Web service.
Welcome to Part 3 of An Extensive Examination of Web Services! In this part we'll examine how to consume a Web service from a client application.
Previously I wrote an article titled Prompting a User to Save When Leaving a Page, which looked at how to use the client-side onbeforeunload event to display a confirmation messagebox when a user attempted to leave a data-entry page after having modified the data's contents without explicitly saving the data.
In the previous installment of this article series, we examined the standards and technologies that make up Web services.
iEntry 10th Anniversary
RSS
Newsletter
Advertising
