Request/Response Pairs: Unterschied zwischen den Versionen
Aus DRV STRING
| Zeile 13: | Zeile 13: | ||
| PaymentRequest || BookingResponse || nur bei Zahlung vor Buchungsabschluß - Buchungsergebnis | | PaymentRequest || BookingResponse || nur bei Zahlung vor Buchungsabschluß - Buchungsergebnis | ||
|- | |- | ||
| − | | | + | | PaymentRequest || PaymentResponse || Standardfall Zahlung nach Buchungsabschluß |
|- | |- | ||
| − | | | + | | ConfigurationRequest || ConfigurationResponse || |
|- | |- | ||
| − | | | + | | ... || ... || ... |
|- | |- | ||
| − | | | + | | ... || ... || ... |
|} | |} | ||
Version vom 1. August 2017, 14:00 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 | Normalfall |
| BookingRequest | PaymentResponse | Zahlung vor Buchungsabschluß |
| PaymentRequest | BookingResponse | nur bei Zahlung vor Buchungsabschluß - Buchungsergebnis |
| PaymentRequest | PaymentResponse | Standardfall Zahlung nach Buchungsabschluß |
| ConfigurationRequest | ConfigurationResponse | |
| ... | ... | ... |
| ... | ... | ... |
