Tip

How will SOAP impact .Net application development?

Kennard Scribner and Mark C. Stiver

How will SOAP impact .Net application development?
Kennard Scribner and Mark C. Stiver

This tip comes from InformIT and examines the prospects of .Net development with other

    Requires Free Membership to View

systems with the use of SOAP. This information can help prepare you for using your existing infrastructure to gain an e-business presence.

--------------------------------------------------------

The architectural model that Microsoft proposes will enhance the traditional client/server relationship you're used to seeing with distributed applications by introducing Microsoft .Net. Normally, a client (such as a browser, but it could be a thick client of any variety) connects to an HTTP server and accesses information internal to the server. The server may implement all manner of n-tier code, access a variety of back office data stores, and apply a vast number of business rules to the client's request. Typically, though, the server presents data internal to that site.

Traditional distributed client/server architecture.

The .Net platform allows you to create any number of web services that provide capabilities, via the Internet, designed to enhance such traditional servers. That is, the client can now connect to a given server, which is then free to easily access information remote from that server, process it in some fashion, and then present the sum of that information to the client.

Distributed client/server architecture using Web Services.

A Web Service is a programmable URI that makes accessing a Web site--or exposing information to be returned from a Web site--as easy as creating and using an object. In a sense, you program your distributed application using resources accessible to you without concern (or with little concern) as to whether those resources are local to your system. Your application's view of the Internet is that the Internet provides a smorgasbord of objects you can interact with to get your job done.

Naturally, the way Web Services deal with each other and with remote clients is by using SOAP, or by employing other, simpler protocols, depending upon their individual natures. This allows you to seamlessly share information with business partners (much like BizTalk) while providing a powerful and easy programming model.

Web Services are created using ASP+ and SDL. They're accessed through the Microsoft .NET Framework, which introduces the C# language (pronounced "C-Sharp", as in the musical notation).

--------------------------------------------------------

Read more about SOAP on InformIT. Registration is required, but it's free.


This was first published in December 2000

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.