Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-11-22 | Add content to diameter_codec(3) and diameter_make(3) | Anders Svensson | |
2012-11-18 | Generate intra-document references | Anders Svensson | |
2012-11-18 | Use entities for cross references | Anders Svensson | |
2012-11-18 | <code> -> <pre> in documentation | Anders Svensson | |
The former doesn't allow seealso content, which erl_docgen doesn't enforce, resulting in mangled PDF. | |||
2012-08-31 | Update copyright years | Björn-Egil Dahlberg | |
2012-08-30 | Correct doc on AVP P flag and add warning about its deprecation | Anders Svensson | |
2011-12-06 | Update documentation | Anders Svensson | |
2011-11-30 | Minor documentation fixes | Anders Svensson | |
2011-08-24 | Merge branch 'anders/diameter/augment_inherited_enums/OTP-9469' into dev | Anders Svensson | |
* anders/diameter/augment_inherited_enums/OTP-9469: Allow @enum when AVP is defined in an inherited dictionary. | |||
2011-08-17 | Allow @enum when AVP is defined in an inherited dictionary. | Anders Svensson | |
3GPP standards (for one) extend the values allowed for RFC 3588 AVP's of type Enumerated. Previously, extending an AVP was only possible by completely redefining the AVP. | |||
2011-08-17 | @id required in dictionary files only when @messages is specified. | Anders Svensson | |
@id defines an application identifier and this is used only when sending or receiving messages. A dictionary can define only AVP's however, to be included by other dictionaries using @inherits, in which case it makes no sense to require @id. Note that message definitions are not inherited with @inherits, only AVP's | |||
2011-05-20 | Various documentation fixes and improvements. | Anders Svensson | |
Added an introductory chapter to the User's Guide as well as more detailed release notes. | |||
2011-05-19 | Fix broken doc links. | Anders Svensson | |
2011-05-18 | Initial commit of the diameter application. | Anders Svensson | |
The application provides an implementation of the Diameter protocol as defined in RFC 3588. |