diff options
author | Fred Hebert <[email protected]> | 2013-01-11 10:31:00 -0500 |
---|---|---|
committer | Fred Hebert <[email protected]> | 2013-01-15 11:45:50 -0500 |
commit | 662d94a531178af005f06b0bfb4a8660b0fa023f (patch) | |
tree | 52bf6e87f4d6b6be23f6170212edc96c0a96704a /examples/tcp_echo/src/echo_protocol.erl | |
parent | 9fd9294a13375a56c42b4b77225bbe317ecf0b4d (diff) | |
download | ranch-662d94a531178af005f06b0bfb4a8660b0fa023f.tar.gz ranch-662d94a531178af005f06b0bfb4a8660b0fa023f.tar.bz2 ranch-662d94a531178af005f06b0bfb4a8660b0fa023f.zip |
Ignore tracking of requests when MaxConn = infinity
There is no need to contact the server and track requests unless being
asked to do so by the user. It's going to be faster and more efficient
to not track anything when being told tracking doesn't matter.
Whenever the max connections is set to infinity, the connections
counting key is not created, or is deleted if it existed already.
When using a numeric value, the connection count is created or
maintained if it existed already.
Moreover, trying to reduce a listener's counter while the max connection
number is set to `infinity` will return 0 and avoid all counting
operations as they are meaningless.
Diffstat (limited to 'examples/tcp_echo/src/echo_protocol.erl')
0 files changed, 0 insertions, 0 deletions