autoStart with custom init #109
Description
I've been unable to successfully take advantage of the autoStart parameter.
autoStart when set to true will start the workers as early as possible. Use this when your workers have to do expensive initialization. That way they'll be ready when the first request comes through.
In my use-case, I'd like my Workers to initialize a connection to another (logging) application (which can take up to several hundred milliseconds) before they start accepting/executing called methods.
It was my understanding that this parameter is present for these cases, when one needs to make expensive initialization. But I could not figure out what is the intended way of implementing such behavior and could find no such examples.