opened
uglybugger
username_0
Some handlers need to have a set maximum number of instances. We've seen this in the wild with spinning up a pool of PhantomJS instances, for instance, as well as where third-party APIs limit incoming connections.

We need a nice way to specify how many concurrently-executing instances of a handler of a particular type should permit, as well as a sensible default.
Per-handler ability to specify maximum concurrent handler instances
issue
closed
DamianMac
username_1
issue