Asynchronous Web Services in .NET Using WSE 2.0

•

What is DaniWeb IT Discussion Community?

You're currently browsing the ASP.NET section within the Web Development category of DaniWeb, a massive community of 391,952 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,836 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our ASP.NET advertiser: Lunarpages ASP Web Hosting

Thread Tools Display Modes

Views: 2634 | Replies: 0

•

Join Date: Feb 2004

Posts: 196

Reputation: ! ! is an unknown quantity at this point

Rep Power: 0

Solved Threads: 0

! !

Offline

Banned

Asynchronous Web Services in .NET Using WSE 2.0

Oct 31st, 2005

•

The ASP.NET Framework does provide support for accessing a Web service asynchronously. The user can wait until the request completes, can block on the WaitHandle, or wait for a callback function to be invoked. However, WSE 2.0 provides a potentially more powerful way of communicating with a Web service by using WS Addressing.

WSE 2.0 is a .NET component that can be downloaded and installed into the .NET Framework. WSE is a Soap Extension that manipulates SOAP messages on both the client side and the server side if implemented in both. It provides a way to communicate by using industry standard SOAP messages, which in turn allows for interaction with Services implemented in other technologies. WSE v2.0 has some classes that allow standardized SOAP messages to be sent based on WS-Addressing, WS-Messaging, and the rest of WS-* specifications.

http://www.codeguru.com/Csharp/Csharp/cs_webservices/tutorials/article.php/c10669/