Changes between Version 4 and Version 5 of Dev/API
- Timestamp:
- Oct 13, 2011, 5:25:53 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified Dev/API
v4 v5 150 150 type:: 151 151 This corresponds to the "Derived type" defined in RFC3588. An AVP can be either defined with a Base Type (!OctetString, Unsigned32, ...) or a Derived Type. In terms of pure parsing, it does not change anything, but defining a Derived Type allows to: 152 * define functions to handle the data with a specific encoding for example (see [http://lists.freediameter.net/pipermail/dev/2011-February/000 143.html this mail] for more details).152 * define functions to handle the data with a specific encoding for example (see [http://lists.freediameter.net/pipermail/dev/2011-February/000055.html this mail] for more details). 153 153 * and/or define constants values for this type. This is a bit different from the Diameter RFC that defines all AVP with constant values as Enumerated type. 154 154