diff options
| author | Anders Svensson <[email protected]> | 2017-06-10 23:40:53 +0200 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2017-06-11 16:30:39 +0200 |
| commit | eadf4efc7e264fe8dd30befb42a42a02cdef58f1 (patch) | |
| tree | 6ac266589946ff35f843cbf89d6913113cbb1629 /lib/diameter/src/app.sed | |
| parent | 034089ed1ba3f78c732edcfc84d85a6ed4a4854e (diff) | |
| download | otp-eadf4efc7e264fe8dd30befb42a42a02cdef58f1.tar.gz otp-eadf4efc7e264fe8dd30befb42a42a02cdef58f1.tar.bz2 otp-eadf4efc7e264fe8dd30befb42a42a02cdef58f1.zip | |
Make diameter_{tcp,sctp} sender configurable
With sends still from the receiving process by default, since changing
the default behaviour may well have negative effects. A separate sender
probably implies a greater need for some form of load regulation for
one, since a blocking send would no longer imply that incoming messages
are no longer recevied. Dealing with this could result in the same
deadlock that the sending process intends to avoid, but the user should
be in control over how/when incoming traffic is regulated.
Diffstat (limited to 'lib/diameter/src/app.sed')
0 files changed, 0 insertions, 0 deletions