diff options
author | Anders Svensson <[email protected]> | 2012-11-19 15:35:05 +0100 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2012-11-19 15:35:05 +0100 |
commit | a636566504740916750419d8d94fd0a28ee672e5 (patch) | |
tree | 70bd9bb5eab1c2fe0b92315c3035971faf3162f4 /lib/diameter/doc/src/notes.xml | |
parent | 2cec24c37208c360123740f3af6b09aa33697f5f (diff) | |
parent | 6a7e9265837bf2521508bd5fbc19b54e1dc4b88f (diff) | |
download | otp-a636566504740916750419d8d94fd0a28ee672e5.tar.gz otp-a636566504740916750419d8d94fd0a28ee672e5.tar.bz2 otp-a636566504740916750419d8d94fd0a28ee672e5.zip |
Merge branch 'maint'
Diffstat (limited to 'lib/diameter/doc/src/notes.xml')
-rw-r--r-- | lib/diameter/doc/src/notes.xml | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/lib/diameter/doc/src/notes.xml b/lib/diameter/doc/src/notes.xml index e57958ac09..aad86b966b 100644 --- a/lib/diameter/doc/src/notes.xml +++ b/lib/diameter/doc/src/notes.xml @@ -1,11 +1,17 @@ <?xml version="1.0" encoding="latin1" ?> -<!DOCTYPE chapter SYSTEM "chapter.dtd"> +<!DOCTYPE chapter SYSTEM "chapter.dtd" [ + <!ENTITY % also SYSTEM "seealso.ent" > + <!ENTITY % here SYSTEM "seehere.ent" > + %also; + %here; +]> <chapter> <header> <copyright> <year>2011</year> +<year>2012</year> <holder>Ericsson AB. All Rights Reserved.</holder> </copyright> <legalnotice> @@ -395,8 +401,7 @@ Known issues or limitations:</p> Some agent-related functionality is not entirely complete. In particular, support for proxy agents, that advertise specific Diameter applications but otherwise relay messages in much the same -way as relay agents (for which a <seealso -marker="diameter_app#handle_request">handle_request/3</seealso> +way as relay agents (for which a &handle_request; callback can return a <c>relay</c> tuple), will be completed in an upcoming release. There may also be more explicit support for redirect agents, although @@ -428,8 +433,7 @@ could likely be expanded upon.</p> <item> <p> -The function <seealso -marker="diameter#service_info">diameter:service_info/2</seealso> +The function &service_info; can be used to retrieve information about a started service (statistics, information about connected peers, etc) but this is not yet documented and both the input and output may change |