ASP.NET
  Home arrow ASP.NET arrow Page 9 - Sample Chapter: Early Adopter Hailstorm (....
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Dedicated Servers  
Moblin 
JMSL Numerical Library 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP.NET

Sample Chapter: Early Adopter Hailstorm (.NET My Services)
By: Tim Pabst
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 3 stars3 stars3 stars3 stars3 stars / 1
    2002-04-08

    Table of Contents:
  • Sample Chapter: Early Adopter Hailstorm (.NET My Services)
  • Making Conversation
  • An Insecure Present
  • SOAP
  • Header
  • Scenario 1: No Response Necessary
  • DIME, not MIME?
  • The Response from HailStorm
  • Summary
  • Conclusion

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


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


    (Page 9 of 10 )

    In this chapter, we have worked through a typical conversation between HailStorm endpoint and server. We have seen that
    • Once a user is authenticated by the Kerberos system in Passport, the Passport ID and Kerberos ticket given the user are then embedded in the request sent to the server to continue the authentication process.
    • Each piece of conversation between endpoint and server is encapsulated in a SOAP message.
    • Each SOAP message includes routing information to the server and back, authentication info, and the request itself.
    • The request is in two parts - an instruction in HSDL (HailStorm Data-manipulation Language) and an XPath expression to identify the part of document the instruction is to be carried out on. We'll cover the formulation of XPath expressions in the next chapter and a description of each HSDL instruction in Chapter 5.
    In next chapter, we'll be taking at look at the structure of the XML documents that we've been querying and how to navigate about them using XPath.

    More ASP.NET Articles
    More By Tim Pabst


     

    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







    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway