| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The code was both broken and incomplete. Now it answers as it should,
albeit using some encode functionality (ie. 3-tuple as diameter_avp
value) that isn't currently documented.
|
| |
|
|
|
|
|
|
|
|
|
| |
Make each example stand on its own by removing the common node module
that just made for more difficult reading, and redo the fairly confusing
transport config: now it's just a list of transport options as passed to
diameter:add_transport/2, along with some syntactic sugar for
transport_module/transport_config pairs.
Also add a healthy README, that should probably be merged into the
documentation.
|
| | |
|
| |\
| |
| |
| |
| | |
* anders/diameter/codec/OTP-14511:
Use map decoding in example client
|
| | |
| |
| |
| |
| |
| | |
As introduced in commit 1b3b64af and adjusted in commit e0603ba1.
There's nothing client-specific about it, but keep the record format in
the server example for the sake of coverage.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
To make them a bit more flexible. Can now do things like this:
server:start([{'Product-Name', "Bob"}]),
server:listen({tcp, [{capx_timeout, 2000}]})
Beware that the latter is completely different from this:
server:listen(tcp, [{capx_timeout, 2000}])
|
| |
|
|
|
| |
Since there's no reason to reject a client that wants to establish
multiple connections, given that diameter can handle it.
|
| |
|
|
|
| |
So as to do what's now recommended in diameter(1), in the grandparent
commit.
|
| |
|
|
|
|
| |
Which hasn't received any attention for some time. Clean it up, rename
the poorly named peer.erl (it's Diameter *nodes* that are implemented),
and make the it possible to specify arbitrary transport configuration.
|
| |
|
|
| |
The timer was renamed in commit abea7186.
|
| |
|
|
|
|
|
|
|
| |
In the same vein as commit 00584303, to avoid logging traffic-related
happenings.
Not that the value in diameter.hrl is just documentation: the value is
set explicitly when diameter:start_service/2 creates diameter_app
records.
|
| |
|
|
| |
In particular, remove the unnecessary list-or-record answer.
|
| |
|
|
|
| |
As it should. The previous discard (surely) pre-dated being able to
return {answer_message, 3001} from a handle_request callback.
|
| |
|
|
|
| |
The output could make it impossible to use the shell. Counters returned
diameter:service_info/2 can be used to check for expected happenings.
|
| |
|
|
|
|
|
| |
Note that the semantics of client:connect/1 have changed slightly: the
second element in an argument 3-tuple is a remote address, the local
address being the transport module's default. Previously it was
interpreted as a common local/remote address.
|
| |
|
|
|
| |
Fix a broken include in example code, remove an inappropriate ct:pal/2
outside of a testcase, echo more info from test/Makefile.
|
| | |
|
| |
|
|
|
| |
Paths changed as a consequence of OTP-9638. Don't use paths under src
however, assume an installation.
|
| |
|
