> The documentation does not state that there is any
> limit on the amount of connections per second. This
> is a bug which needs to be fixed. 

You are right, this is a *very* minor bug, which will be fixed.

> What makes you think that using %c10 will not result
> in exactly the same problem in an unlucky
> scheduling?
This has absolutely nothing to do with scheduling.

> Your program is simply not robust; it is broken. 

You can not expect correct behavior when using insane values as parameters
input. Attempting to use 3000 connections per seconds in a browser/client is
simply not reasonable.

> Conclusion, either fix the program or stop
> misleading people by providing wrong documentation. 

Not sure if trolling, or just very rude :)