Request/Response Pairs: Unterschied zwischen den Versionen

Aus DRV STRING
Wechseln zu: Navigation, Suche
Zeile 7: Zeile 7:
 
! Request !! Response !! Notes
 
! Request !! Response !! Notes
 
|-
 
|-
| BookingRequest || BookingResponse || Normalfall
+
| BookingRequest || BookingResponse || standard case
 
|-
 
|-
| BookingRequest || PaymentResponse || Zahlung vor Buchungsabschluß
+
| BookingRequest || PaymentResponse || payment before booking
 
|-
 
|-
| PaymentRequest || BookingResponse || nur bei Zahlung vor Buchungsabschluß - Buchungsergebnis
+
| PaymentRequest || BookingResponse || only in case of payment before booking - booking completed
 
|-
 
|-
| PaymentRequest || PaymentResponse || Standardfall Zahlung nach Buchungsabschluß
+
| PaymentRequest || PaymentResponse || standard case payment after booking
 
|-
 
|-
 
| ConfigurationRequest || ConfigurationResponse ||  
 
| ConfigurationRequest || ConfigurationResponse ||  
 
|-
 
|-
| ... || ... || ...
+
| VersionRequest || VersionResponse ||  
 
|-
 
|-
| ... || ... || ...
+
| AgencyClearanceRequest || AgencyClearanceResponse ||  
 
|}
 
|}

Version vom 1. August 2017, 14:32 Uhr

The STRING interface contains matched request/response pairs. In most cases the response will be of the same kind as the request, but under certain conditions deviations will be allowed.

As XSD schema can't define workflows of this kind we keep a table of allowed request-response pairs here.

Request Response Notes
BookingRequest BookingResponse standard case
BookingRequest PaymentResponse payment before booking
PaymentRequest BookingResponse only in case of payment before booking - booking completed
PaymentRequest PaymentResponse standard case payment after booking
ConfigurationRequest ConfigurationResponse
VersionRequest VersionResponse
AgencyClearanceRequest AgencyClearanceResponse