Matt Yule-Bennett

Thanks :) This isn't as easy to achieve as it should be. You could subclass the `RpcConsumer` with hardcoded options and pass them to the `Queue` when it's instantiated in...

For posterity, getting this to work requires updating `__params` when you set properties on an extension after instantiation (otherwise they'll be lost when you `bind`), or moving the whole extension...

Thank you for this @vlcinsky. I wonder if it makes more sense to raise an error if the broker is undefined though, or use a default value? `nameko shell` is...

Hi @ravjanga Nameko already does some of this for you with its `call_stack`. The built-in extensions at least keep track of previous call history in the worker context, so that...

Completely agree with @signalpillar, and we did the exact same thing -- the ELK stack fed by nameko-tracer was a home-grown distributed tracing solution; in hindsight, it would have been...

I don't understand this request. Do you have an example?

There is some overlap here with https://github.com/clef/flask-nameko. Connection pooling is clearly a use-case we need to support. The performance improvement is very significant! We intentionally made the standalone package independent...

This could be enhanced to instantiate proxies only on demand, no? With that change (and using non-eventlet primitives) this would be an enhancement of nameko's out-of-the-box offering. It would be...

Great stuff, thanks. Looking forward to the results!

@jessepollak there is some overlap here with our recent [mailing list thread](https://groups.google.com/forum/#!topic/nameko-dev/woyoV9Iz5mk). I think the ideal API here has the following qualities: - Is backwards compatible with the existing proxy...