> On Sep 21, 2017, at 11:01 AM, Alex Blewitt via swift-dev > <swift-dev@swift.org> wrote: > > One of the key reasons why you would want to handle those situations is that > you may have a leak or other resources, but you may also be handling 99,999 > other requests at the same time that you don't want to drop on the floor. > > Even if you put the server into some kind of degraded mode (for example, > taking it out of load balancer rotation) and let the requests drain > naturally, it's still a lot better than terminating everything immediately. > > This isn't an issue in single-user applications but when you have > hundreds/thousands of simultaneous users it does limit where crashing the > process makes sense. > > (Of course, if the server really is deadlocked, then it's going to go down > anyway; but if other parts can continue running then why not?)
There's a thread for this topic on swift-evolution. It'd be good to keep the discussion focused there. -Joe _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
