Configuration: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Inhalt gelöscht Inhalt hinzugefügt
Keine Bearbeitungszusammenfassung |
Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
In past interfaces many values were added to transactions which almost never changed or at least were not updated on short notice. STRING moves them to a separate configuration query which is supposed to be executed by clients in a much lower frequency, for instance once per day and operator. In the meantime the values returned should be cached / stored locally. |
|||
One the one hand this query will return basic operator data like address, insolvency insurance and so on. On the other hand it provides a set of limitations and features of the operator system which are not by itself defined in the schema, for instance the maximum number of travellers in a request. |
|||
[...] |
|||
* ConfigurationRequest (evtl. später mit Kategorien) |
* ConfigurationRequest (evtl. später mit Kategorien) |
||
* ConfigurationResponse enthält Merkmal-Werte-Paare, die extern definiert werden |
* ConfigurationResponse enthält Merkmal-Werte-Paare, die extern definiert werden |
||
Version vom 25. Mai 2018, 09:34 Uhr
In past interfaces many values were added to transactions which almost never changed or at least were not updated on short notice. STRING moves them to a separate configuration query which is supposed to be executed by clients in a much lower frequency, for instance once per day and operator. In the meantime the values returned should be cached / stored locally.
One the one hand this query will return basic operator data like address, insolvency insurance and so on. On the other hand it provides a set of limitations and features of the operator system which are not by itself defined in the schema, for instance the maximum number of travellers in a request.
[...]
- ConfigurationRequest (evtl. später mit Kategorien)
- ConfigurationResponse enthält Merkmal-Werte-Paare, die extern definiert werden