| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
This reverts commit d4e4511b19f4126d9271a6e3a8fa2eb716da7e85.
|
| | |
|
| |
|
|
| |
This reverts commit 1cf126f91eb533783409da95b117207d8c13d9aa.
|
| | |
|
| |
|
|
| |
This reverts commit 587341d994f91af5b30483ee9434e932e3d7b802.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit a2c8df222e6d02fa518d5d6cbbea75a9dd720d30.
|
| | |
|
| |
|
|
| |
This reverts commit 435bc5e68dd45ff6f7992077998930519208e910.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
* maint:
Updated OTP version
Prepare release
Update copyright year
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
* maint:
Updated OTP version
Prepare release
# Conflicts:
# OTP_VERSION
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
xmerl has to be able to parse the file in order for the
docgen link validator to work.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We add `seemfa`, `seeerl`, `seetype`, `seeapp`, `seecom`, `seecref`
, `seefile` and `seeguide` in order to make it easier to reason
about what each link points to without examining the target.
This information will then be embedded in the EEP-48 chunks for
usage by other tools.
The tool used can be found here:
https://gist.github.com/garazdawi/68527d92ae5b37c8f129bfbdfffdfa68
|
| |
|
|
|
| |
Some seealso need to be fixed manually and some need to
be modified for the script to find them.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* maint:
Updated OTP version
Prepare release
# Conflicts:
# OTP_VERSION
# erts/doc/src/socket.xml
|
| | | |
|
| |\ \
| |/
| |
| |
| | |
* maint:
Update copyright year
|
| | | |
|
| |\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
* maint:
Updated OTP version
Prepare release
# Conflicts:
# OTP_VERSION
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Service options passed to diameter:add_transport/2 were interpreted as
such, instead of being ignored as the documentation requires, with the
consequence that outgoing and incoming requests saw different values of
some options (eg. decode_format), some were always taken from transport
options (eg. restrict_connections), and others from service options
(eg. share_peers/use_shared_peers). Now ignore service options passed
to diameter:add_transport/2, as the documentation requires.
This behaviour precedes the changes in commit 5f3becad, that the parent
commit addresses, and has probably been the case for some time.
That unknown options passed to diameter:add_transport/2 are ignored
rather than rejected is questionable, but at least one known user makes
use of this to be able to identify transport options returned from
diameter:service_info/2, so it can't just be removed. That service
options in transport configuration isn't rejected outright is probably
even more questionable, but it hasn't been an issue in practice.
The documentation was also a little wrong on which transport options can
be configured on a service, missing transport_config and
transport_module as two that aren't allowed, although these did cause
diameter:start_service/2 to return error as expected. (That function not
accepting unknown options.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit f1cdd721 documented the possibility of starting a handler process
for an incoming Diameter request with a configured MFA, but the counter
implementation (ie. {traffic_counters, true}) was broken when this
process was not on the same node as the transport configuration:
incrementing a counter was a noop since the transport pid was not
associated with the transport reference in diameter_stats on the remote
node.
This was a good thing though, since distributing the counters across
handler nodes has a number of problems: not losing counters if the
connection to a handler node is lost, or not being able to remove
counters on a handler node when the transport is removed, keeping track
of where counters are located if they have to be retrieved from multiple
nodes, and so on. Moreover, it's the service/transport configuration on
the local node that orders the counters, so incrementing them on remote
nodes is questionable.
Avoid the problems by incrementing counters where the transport in
question is configured, the node that terminates any associated peer
connection. Instead of calling diameter_stats to increment the counter
when the diameter_peer_fsm process it's being incremented for is not
local, bang the counter to that process to let it call diameter_stats.
The only requirement on the handler node is now that diameter and
application callbacks reside on the code path, and the documentation has
been updated to reflect this.
Compare this to the case of outgoing requests, where counters are
incremented on the originating node. Similarly, it's the local
configuration that orders the counters, and there can be multiple
remote nodes through which the request can be sent on a peer connection
just like there can be multiple handler nodes in the case of an incoming
request.
|
| | |
| |
| |
| |
| | |
The variable can be set to pdf, html, man or chunks
and also any combination of the above.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* anders/diameter/distribution/OTP-15398:
Add diameter_dist_SUITE to exercise diameter_dist:route_session/2
Add consistent hashing to diameter_dist:route_session/2
Add options to diameter_dist:route_session/2 node selection
Add diameter_dist for ready spawn_opt callbacks
Tweak/document request handler callback
Document acknowledgements in transport interface
Fix comment typo
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The possibility of configuring an MFA as spawn_opt was added in commit
fd285079, the callback being passed an arity-0 fun to be applied in an
appropriate handler process. Replace the fun by a tuple to be passed to
diameter_traffic:request/1, to avoid passing funs between nodes when
handler processes are remote.
A list-valued spawn_opt is now equivalent to the following configured as
{spawn_opt, {Mod, spawn_local, [Opts]}}.
spawn_local(ReqT, Opts) ->
spawn_opt(diameter_traffic, request, [ReqT], Opts).
ReqT is passed by diameter and contains information that the callback
may want to decide where to handle the request in question (which wasn't
accessible with a fun), but this information isn't exposed in a
documented way. The intention is instead to add an own callback
implementation to make use of the information.
Note that application lookup now takes place in the watchdog process in
both the list-valued (or no configuration) and mfa-valued cases. Whether
this is good, bad, or (probably) inconsequential remains to be seen.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the {diameter, ack} message from a transport process to its
parent that requests that every Diameter request passed to the parent be
matched by a incoming send message, the atom false replacing a message()
in the case that the request is unanswered, allowing the transport to
keep track of the number of outstanding requests.
These were added in commit ca09cf7b, and are used to implement the
message_cb config in diameter_tcp/sctp, documented in commit cefcaa5c.
This commit documents the interface, to make it available to other
transport implementations.
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
* maint-20:
Updated OTP version
Prepare release
|
| | | | |
|
| | |/
|/|
| |
| | |
introduced after OTP_R13B03.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
