Prompted by a question on the python library implementation, I am wondering about the following:
If a DSO sends a FlexRequest to a AGR, but the AGR wants to reject that request for a functional reason (like "Invalid Sender", "Invalid Message", etc, as specified in on page 28 of the PDF specification), the AGR can do so in a FlexRequestResponse message.
But what if the DSO receives a FlexRequestResponse message from an AGR that is not correct, for instance: containing an unknown FlexRequestMessageID, how do we let the AGR know? What message do we wrap this in? Or does the protocol not expect us to ever reject a 'Response' message? It seems that we are not supposed to reject it using a HTTP status code, because the message passed XML validation.
(I used to return information like this is the synchronous response, but that is also not described in the protocol, so I'm removing this from the Python implementation).
Thanks!
Prompted by a question on the python library implementation, I am wondering about the following:
If a DSO sends a
FlexRequestto a AGR, but the AGR wants to reject that request for a functional reason (like "Invalid Sender", "Invalid Message", etc, as specified in on page 28 of the PDF specification), the AGR can do so in aFlexRequestResponsemessage.But what if the DSO receives a
FlexRequestResponsemessage from an AGR that is not correct, for instance: containing an unknownFlexRequestMessageID, how do we let the AGR know? What message do we wrap this in? Or does the protocol not expect us to ever reject a 'Response' message? It seems that we are not supposed to reject it using a HTTP status code, because the message passed XML validation.(I used to return information like this is the synchronous response, but that is also not described in the protocol, so I'm removing this from the Python implementation).
Thanks!