- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Fri, 17 Jan 2003 10:07:25 -0500
- To: www-tag@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ noah_mendelsohn@us.ibm.com was heard to say:
| <s:Envelope>
| <s:Header>
| <? AAA BBB CCC ?>
| <n1:yourHeader1 role=intermed1">
| ...
| </n1:yourHeader1>
| <? XXX YYY ZZZ ?>
| <n2:yourHeader2 role=intermed2">
| ...
| </n2:yourHeader2>
| </sHeader>
| <s:Body>
| <z:purchaseOrder>
| </z:purchaseOrder
| </s:Body>
| </s:Envelope>
|
| what do I do at an intermediary where the first header
| is processed? The SOAP model says that when the
| message is received at intermed1, n1:yourHeader1 will
| be processed, and all things being equal that header
| will be removed before the message is relayed to
| intermed2. Which, if any, of the PIs should be
| removed? Note that if none are removed, the resulting
| message is:
It seems to me that if the PI target "AAA" was related to processing
'n1:yourHeader1' the processor for that header would have known about
it and could have removed it.
But SOAP forbids PIs in the header and that's fine by me.
I don't see, in theory, how the problem is really different from
<s:Envelope>
<s:Header>
<myns:ignoreTheNextHeader/>
<n1:yourHeader1 role=intermed1">
...
</n1:yourHeader1>
<myns:increaseThePriorityOfTheNextHeader/>
<n2:yourHeader2 role=intermed2">
...
</n2:yourHeader2>
</sHeader>
<s:Body>
<z:purchaseOrder>
</z:purchaseOrder
</s:Body>
</s:Envelope>
But (obviously! :-) I haven't read the SOAP spec well enough to know
if that's covered or not.
Be seeing you,
norm
- --
Norman.Walsh@Sun.COM | Next to knowing when to seize an opportunity,
XML Standards Architect | the most important thing in life is to know
Web Tech. and Standards | when to forego an advantage.--Benjamin
Sun Microsystems, Inc. | Disraeli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE+KBwtOyltUcwYWjsRAmFCAJ9Fhx1MVm0fYeVFPKdYSrw+0YzN/gCgnZb+
U04tKJMIvaQ1T6ObcfbjWWc=
=2zji
-----END PGP SIGNATURE-----
Received on Friday, 17 January 2003 10:07:46 UTC