Re: Issue 68 - status information

Is this not already supported by header blocks anyway (i.e. you could define a
new header block for exactly that purpose), or am I missing something?

Jean-Jacques.

Oisin Hurley wrote:

> Excerpt from the agenda:
>
> >. Issue 68, convey status information [13] (1.25 + 15)
> >Requirement 703b [14] says ".... must define a mechanism or mechanisms to
> >allow the transfer of status information within an XMLP message without
> >resort to use of XMLP fault messages....". We need to clarify what exactly
> >is meant by this requirement, decide whether or not to keep it, and if so
> >how do we resolve it.
>
>   .. the intent behind this requirement was to allow information not
> related to the results of an operation to flow back with a
> response - the use case being that status information could be put in
> the message without having to resort to using fault messages. I can't
> recall with any clarity exact details of what was required - it is also
> with limited recall that I think Ray Denenberg may have been the source
> of this requirement. Ray, can you confirm or deny?
>
>  cheers
>   --oh

Received on Tuesday, 13 November 2001 03:59:14 UTC