Changes between Version 2 and Version 3 of Dev/API

Timestamp:

Mar 1, 2011, 5:27:14 PM (13 years ago)

Author:

Sebastien Decugis

Comment:

--

Dev/API

@@ -149 +149 @@
 
  type::
-   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:
+   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:
    * define functions to handle the data with a specific encoding for example (see [http://lists.freediameter.net/pipermail/dev/2011-February/000143.html this mail] for more details).
    * 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.
@@ -159 +159 @@
 
  AVP::
-   This object associates AVP code and vendor to its name, flags, and basic type, which allows for parsing the Diameter message and interpreting the content of the AVP (for example, we can learn if an AVP containts OctetString data or if this is a Grouped AVP containing other AVPs in its data portion). Optionaly, the AVP can be associated with a Derived Type when it is created, which allows some additional features.
+   This object associates AVP code and vendor to its name, flags, and basic type, which allows for parsing the Diameter message and interpreting the content of the AVP (for example, we can learn if an AVP containts !OctetString data or if this is a Grouped AVP containing other AVPs in its data portion). Optionaly, the AVP can be associated with a Derived Type when it is created, which allows some additional features.
 
  command::