"Ann W. Harrison" <aharrison@...> wrote:

>
> How does the server-side timeout recognize the difference between a
> badly-designed Crystal Report that takes forever, and one that is as
> good as it can be, is absolutely required, and takes nearly forever?

Those who cannot analyze their load and recognize the difference just won't
be using this feature. How does DBA decide that 10 attachments per second is
a valid value whilst 20 ones mean a DoS attack? How does DBA decide to limit
the maximum number of concurrent requests in the system? What about disk and
CPU quotas? I agree there are cases where this feature is useless, but it
doesn't mean it's bad for everyone.


Dmitry