| Age | Commit message (Collapse) | Author |
|---|
|
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}])
|
|
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.
|
|
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.
|
|
The output could make it impossible to use the shell. Counters returned
diameter:service_info/2 can be used to check for expected happenings.
|
|
Paths changed as a consequence of OTP-9638. Don't use paths under src
however, assume an installation.
|
|
|
