I like the queueing behavior rather than Server Busy. If it takes a long time, people will know the server is busy and can either wait or not. If it spits back Server Busy, they have to keep hitting Reload.
One good thing about having a connection queue separate from the listen queue is that it can be used for better wait time statistics. > > On Saturday, September 29, 2001, at 08:41 AM, Dossy wrote: > > I'm still curious as to why the busy message was gotten rid of > > in the AOLserver 3.x tree > That facility was mostly provided for internal high-traffic sites within > AOL when the sites ran 2.3.3, which couldn't keep up with the load. The 3. > x version was so much faster that the feature was no longer necessary. It > didn't always work, either, and it was a real pain to debug. >
