org.mashupbots.socko.webserver
Read configuration from AKKA's application.conf.
Read configuration from AKKA's application.conf. Supply default values to use if setting not present
Disable Nagle's algorithm. Defaults to true if not supplied.
Set a hint the size of the underlying buffers for outgoing network I/O.
Get the size of the buffer actually used by the platform when receiving in data on this socket.
Turn on socket keep-alive. Defaults to false if not supplied.
Enable reuse address for a socket and not throw an "already bind exception" The default value is JVM specific.
Specify a linger-on-close timeout.
Sets the type-of-service or traffic class field in the IP header for a TCP or UDP socket. \ The default value is JVM specific.
The number of requests that can be queued. Useful in managing sudden bursts in requests. If take an example with a socket server invoker that has max pool set to 300, accept threads is 2, and backlog is 200, will be able to make 502 concurrent client calls. The 503rd client request will get an exception immediately. However, this does not mean all 502 requests will be guaranteed to be processed, only the first 300 (as they have server threads available to do the processing). If 202 of the server threads finish processing their requests from their initial client connections and the connection is released before the timeout for the other 202 that are waiting (200 for backlog and 2 for accept thread), then they will be processed (of course this is a request by request determination).
The number of requests that can be queued.
The number of requests that can be queued. Useful in managing sudden bursts in requests. If take an example with a socket server invoker that has max pool set to 300, accept threads is 2, and backlog is 200, will be able to make 502 concurrent client calls. The 503rd client request will get an exception immediately. However, this does not mean all 502 requests will be guaranteed to be processed, only the first 300 (as they have server threads available to do the processing). If 202 of the server threads finish processing their requests from their initial client connections and the connection is released before the timeout for the other 202 that are waiting (200 for backlog and 2 for accept thread), then they will be processed (of course this is a request by request determination).
Turn on socket keep-alive.
Turn on socket keep-alive. Defaults to false if not supplied.
Disable Nagle's algorithm.
Disable Nagle's algorithm. Defaults to true if not supplied.
Get the size of the buffer actually used by the platform when receiving in data on this socket.
Enable reuse address for a socket and not throw an "already bind exception" The default value is JVM specific.
Set a hint the size of the underlying buffers for outgoing network I/O.
Specify a linger-on-close timeout.
Sets the type-of-service or traffic class field in the IP header for a TCP or UDP socket.
Sets the type-of-service or traffic class field in the IP header for a TCP or UDP socket. \ The default value is JVM specific.
TCP IP configuration as per Netty.
See javadoc and netty doc for more information.
Netty and JVM defaults are used until overriden here.
Disable Nagle's algorithm. Defaults to
trueif not supplied.Set a hint the size of the underlying buffers for outgoing network I/O.
Get the size of the buffer actually used by the platform when receiving in data on this socket.
Turn on socket keep-alive. Defaults to
falseif not supplied.Enable reuse address for a socket and not throw an "already bind exception" The default value is JVM specific.
Specify a linger-on-close timeout.
Sets the type-of-service or traffic class field in the IP header for a TCP or UDP socket. \ The default value is JVM specific.
The number of requests that can be queued. Useful in managing sudden bursts in requests. If take an example with a socket server invoker that has max pool set to 300, accept threads is 2, and backlog is 200, will be able to make 502 concurrent client calls. The 503rd client request will get an exception immediately. However, this does not mean all 502 requests will be guaranteed to be processed, only the first 300 (as they have server threads available to do the processing). If 202 of the server threads finish processing their requests from their initial client connections and the connection is released before the timeout for the other 202 that are waiting (200 for backlog and 2 for accept thread), then they will be processed (of course this is a request by request determination).