Hello,
I'm not sure if this is in Grizzly proper or left to user code but here's what I want to express:
If a useful message cannot be assembled in n-seconds, kill the connection.
Say there is a connection established by a client. There is a fixed header (which contains the size of the message body to follow) followed by a variable length message body.
How would one express the notion that the client is just too damned slow? Accidentally (fine, network congestion) or deliberately (dribble in one byte just enough to keep the connection alive and consume server resources for long periods).
I'm also curious how to deal with suppressing SSL renegotiations just endlessly cycling through ciphers. Perhaps the "too damned slow" rule would handle this as well.
Any pointers to sample code?
thanks,
greg