My third issue

Hi,

I meant to send this issue earlier, but:

In X-BULK we had a StatusRequest / StatusResult message
set that allowed a server to query the state of an outstanding
batch without grabbing the entire result. Now that we have
compound in XKMS, do we want StatusRequest/StatusResult messages?

I would envision something like HTTP HEAD - it returns detail
to the level of ResultAbstractType; i.e., ResultMajor/Minor.
This would allow a workflowy-type system to easily find the
status of a request. When requesting the status of a batch,
the same level of detail is returned for each individual req
in the batch.

        <element name="StatusRequest" type="xkms:StatusRequestType"/>
        <complexType name="StatusRequestType">
                <complexContent>
                        <extension base="xkms:RequestAbstractType">
                                <attribute name="ResponseId" type="anyURI" use="optional"/>
                        </extension>
                </complexContent>
        </complexType>

        <element name="StatusResult" type="xkms:StatusResultType"/>
        <complexType name="StatusResultType">
                <complexContent>
                        <extension base="xkms:ResultAbstractType"/>
                </complexContent>
        </complexType>

        <!-- Status of a compound request -->
        <complexType name="CompoundStatusResultType">
                <complexContent>
                        <extension base="xkms:StatusResultType">
                                <sequence minOccurs="0" maxOccurs="unbounded">
                                        <element ref="xkms:StatusResult"/>
                                </sequence>
                        </extension>
                </complexContent>
        </complexType>

We do have PendingNotification which in some sense could provide
the same level of reporting; however, it is not well defined where
StatusRequest is simple and standard.

merlin

Received on Thursday, 12 December 2002 08:39:20 UTC