By considering the server creation and starting out-of scope, rog's approach in-effect assumes that a worker instance is the same as a worker "run". Once a worker "w" is created it is considered "running" and once it's stopped, there is no way to re-start it. You must create a new instance. This sidesteps most of the issues. In fact the worker "w" is a single-use thing much like a context.
/npat (sent from my mobile) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
