Hi, On Fri, Jul 18, 2014 at 10:58:30AM -0600, Eduardo Silva wrote: > Hi Everybody, > > in the incoming major release Monkey v1.6 that will be the base too > for Duda I/O stable branches dst-2 (dst-1 is based on 1.4), there is a > new feature named "Overcapacity", it basically address the following > scenario (example): > > - Your server or web service is configured to handle up to 1000 > concurrent connections (all of them opened at the same time). > - You get 1200 concurrent connections. > > The behavior for this situation is very important as it may address > different requirements of business needs, so the Overcapacity feature > have 3 modes: > > 1) Drop : just drop any new incoming connection. > 2) Resist : try to serve all request, even some of them may delay. > 3) TooBusy: report a 503 Service Unavailable HTTP status.
Some people in REST API world recommend use the code 202, which means "OK, I received your, it was OK, but I'm not ready yet to give you an answer", this let clients to retry after X seconds/minutes. > > This is real world scenario where sadly no one of other Web Servers > have some setup for this, just a hard coded action, personally i will > make some noise about this as they should implement it. Does it really need to be hardcoded?, because I'm thinking two possible scenarios where your server is gonna be overloaded: 1.- DDoS, if you're under in this situation, then you want to just drop the connection, you don't want to be polite. 2.- Honest overload of the server, because there is a peak of honest users, then you may want to return something like Error 202, so clients can acknowledge the problem and display a friendly message to the user, Error 503 is basically "the server is dead, probably the sysadmin will have to do someting" (at least that's what I interpret when I get that error). Best Regards, -- _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
