Re: Proposal: Module for checking mustUnderstand headers have been processed

I was only dealing with the ultimate destination case but thinking about it
if all actors dealt with it the same way it would give us the ability to
have this thing checked at any point in the chain.

The problem is though that without any notion of path it's only the ultimate
destination that knows all other actors should have done their stuff. Any
actor in the chain would not know if a targetted mustunderstand='1' block
had been missed or had not yet reached the intermediary it was targetted at
:-(

So, it depends on what we want to do. I would say that for now, actor is not
allowed on this header. If we later get some notion of path/ordering maybe
we could allow it at that point.

Gudge

----- Original Message -----
From: "Doug Davis" <dug@us.ibm.com>
To: "Martin Gudgin" <marting@develop.com>
Cc: "XML Protocol Comments" <xml-dist-app@w3.org>
Sent: Thursday, May 10, 2001 8:17 PM
Subject: Re: Proposal: Module for checking mustUnderstand headers have been
processed


> Martin,
>   How do you see the "actor" attribute playing into this?  What does it
> mean for this new header to be targeted at something other than the
> ultimate destination?  I guess it only really becomes a problem when
> that actor is actually hit. 8-)  I guess it should fault.....?
> -Dug
>

Received on Thursday, 10 May 2001 16:13:08 UTC