[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Relevent XML Protocols discussion on headers, routing and faults.
Background: XMLP is having a lengthy discussion on the processing model around headers an intermediaries, more specifically: - how xmlp messages are routed via intermediaries, - how an intermediary is told it must understand a header, - how an intermediary a header is for it, - how an intermediary reports a fault, - how intermediaries determine header dependency, - how profiles of intermediares are specified - can headers be re-ordered - what is the steps or model of processing headers - what are the transaction rollbacks of header processing required for an intermediary that must understand many headers and finds an error partway through - and how an end-recipient of a messages knows whether all the appropriate intermediaries understood. The key SOAP constructs that are being discussed are the mustUnderstand attribute, the Actor Attribute, the use of Fault wrt headers, and the Envelope. Almost every aspect of this discussion implies changes to SOAP 1.1 as S11 does not appear to be sufficient to explain the usage of the attributes and elements. All of this seems extremely relevent to any SAML binding into SOAP headers, especially if we have SAML assertions as headers with a SAML RP as an intermediary to a particular application. The most informative (as usual from Noah) is a bit long but really gets into the issue of SOAP, mustUnderstand, etc. http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0220.html In it, there is a very interesting proposal to add a "dependsUpon" attribute, that points to other headers. As well, there is the notion of modify headers after processing - such as modifying a SAML header - to indicate that it "hasHappened". Henrik wrote an interesting response at http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0231.html Glenn Daniels also posted a proposal on how faults in headers could be indicated at http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0218.html Finally, Henrik also noted how describing header ordering in a particular message is like describing general message flow ala WSDL, http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0254.html There are many more great pieces of information, but I don't think many people will have read these 4 pieces. If any of you have made it completely through all 4 responses, you're probably in the top 5% of the SAML class on this homework assignment and get a gold star :-) Cheers, Dave Orchard XML Architect Jamcracker Inc., 19000 Homestead Dr., Cupertino, CA 95014 p: 408.864.5118 m: 604.908.8425 f: 408.725.4310 www.jamcracker.com - Sounds like a job for Jamcracker.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC