I understand your intentions of disconnecting flooders. I am just
suggesting that you use time stamps with your CLIENT_FLOOD threshold. So
that if a client's receive queue exceeds a certain amount of bytes in a
given period of time, then disconnect it.
That way the client can pace the amount of data it sends, without having
to do it heuristically.
Onn Fri, 4 May 2001, Perry Lorier wrote:
> On Wed, May 02, 2001 at 11:30:59AM -0400, [EMAIL PROTECTED] wrote:
> > Thanks for clearing that up.
> >
> > How should a client be programmed such that the receive queue never grows
> > above CLIENT_FLOOD? Should it control the amount of text per given time?
> > The client has no knowledge of how large the receive queue is on the
> > server.
> >
>
> We could remove clients from the read list when their recieve q has filled up.
> But the point of client_flood was to catch clients that were flooding and
> disconnecting them :)
>
>
