Home arrow ASP.NET arrow Page 5 - Sample Chapter: Early Adopter Hailstorm (.NET My Services)
ASP.NET

Sample Chapter: Early Adopter Hailstorm (.NET My Services)


Microsoft's .NET My Services is a family of XML web services that improves operational functionality of .NET applications and web pages. In this article Tim takes a look at a sample chapter from Wrox's "Early Adopter Hailstorm (.NET My Services)" book. The chapter talks about what exactly .NET My Services are and how they are composed amongst other things.

Author Info:
By: Tim Pabst
Rating: 5 stars5 stars5 stars5 stars5 stars / 11
April 08, 2002
TABLE OF CONTENTS:
  1. · Sample Chapter: Early Adopter Hailstorm (.NET My Services)
  2. · Making Conversation
  3. · An Insecure Present
  4. · SOAP
  5. · Header
  6. · Scenario 1: No Response Necessary
  7. · DIME, not MIME?
  8. · The Response from HailStorm
  9. · Summary
  10. · Conclusion

print this article
SEARCH DEVARTICLES

Sample Chapter: Early Adopter Hailstorm (.NET My Services) - Header
(Page 5 of 10 )

The <path> header, as defined by the SOAP Routing Protocol, lets the creator of the message define its ultimate destination and the routes that message and replies will take to get there and back. It is a mandatory part of every HailStorm message, be it request or response.

<srp:path>

<srp:action>

http://schemas.microsoft.com/hs/2001/10/core#request</srp:action>

<srp:to>http://this.cluster.myContacts.msn.com/danm@wrox.com/</srp:to>

<srp:fwd>

<srp:via/>

</srp:fwd>

<srp:rev>

<srp:via/>

</srp:rev>

<srp:id>uuid:764CBFB8-A9FF-46D0-BAEC-3D11F9AA44A8</srp:id>

<srp:relatesTo/>

</srp:path>


The constituent sub-elements of <path> are described in the table below.



The route from endpoint to server and back can involve several intermediaries that know how to receive and send on SOAP messages as required. It might also make use of several transport protocols as well. SOAP-RP currently allows us to define a path over the synchronous messaging protocols HTTP, UDP, and TCP only, but the need to support asynchronous messaging over SMTP as given in the SOAP specification should mean that SMTP will also be supported soon. Other messaging systems like Microsoft's MSMQ, IBM's MQSeries, .NET Remoting, and the Java Message Service (JMS) also have the capacity to send and receive SOAP messages as either intermediaries or endpoints.

Synchronous Messaging via HTTP

The HTTP request/response model mirrors that of SOAP almost perfectly and is the protocol of choice for synchronous messaging using SOAP. If a secure connection is required, HTTPS (HTTP + SSL) can be used in exactly the same fashion. It's generally recommended to use the HTTP POST request to send your SOAP message, as this will keep it hidden, as opposed to HTTP GET, which will attempt to append it to the destination URI. Indeed, the SOAP 1.1 specification provides details for binding SOAP to HTTP POST. It's all in the header.

POST /MyContacts HTTP/1.1

Content-Type: text/xml; charset="utf-8"

Content-Length: yyyy

SOAPAction : " http://schemas.microsoft.com/hs/2001/10/core#request "

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"

...


The key lines of the HTTP header, specifying that the request contains an XML document using the utf-8 character set (HailStorm uses only utf-8 encoding) and that it is a HailStorm request are highlighted. In response, a SOAP message with the header:

HTTP/1.1 200 OK

Content-Type: text/xml; charset="utf-8"

Content-Length: zzzz


is returned if the query worked and the SOAP message following the header contains a response indicating success. If, however, something went wrong on the server and an attempt to processing your query generated a SOAP Fault, the response header will always take this form:

HTTP/1.1 500 Internal Server Error

Content-Type: text/xml; charset="utf-8"

Content-Length: zzzz


There are several different scenarios using HTTP we can hypothesize now, which should be working when HailStorm becomes a reality next year.
blog comments powered by Disqus
ASP.NET ARTICLES

- How Caching Means More Ca-ching, Part 2
- How Caching Means More Ca-ching, Part 1
- Reading a Delimited File Using ASP.Net and V...
- What is .Net and Where is ASP.NET?
- An Object Driven Interface with .Net
- Create Your Own Guestbook In ASP.NET
- HTTP File Download Without User Interaction ...
- Dynamically Using Methods in ASP.NET
- Changing the Page Size Interactively in a Da...
- XML Serialization in ASP.NET
- Using Objects in ASP.NET: Part 1/2
- IE Web Controls in VB.NET
- Class Frameworks in VB .NET
- Cryptographic Objects in C#: Part 1
- Sample Chapter: Pure ASP.Net

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 
Support 

Developer Shed Affiliates

 




© 2003-2017 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials