Kevin Ingelman

I'm guessing this probably relates to this commit: http://github.com/tobi/delayed_job/commit/d0a9c2d5044746445ec7beebf3f0ca62ea12c525

I would disagree that the correct behavior is to dequeue items of the same priority in random order; calling it a queue implies that order should be maintained. http://en.wikipedia.org/wiki/Queue_%28data_structure%29

If it's not a ton of work I think it still might be worthwhile to default `thriftFramed` and `thriftProtocol` on the client to to match whatever is set on the...

Fair enough, I forgot about the multiple servers case.

@amitsaha Sorry for the delay. By RPC do you mean thrift? We could definitely make something work for TTwitter thrift, but not sure if there's an option for native thrift....

Hey @adriancole, good question. As far as I know there aren't any other open issues for adopting additional trace header formats. Since we use the `l5d-ctx-*` headers to propagate both...

Yeah, that makes sense. Linkerd could provide a pluggable server-side filter that converts inbound headers to a finagle Trace object, and a pluggable client-side filter that converts the Trace object...

Good thinking -- I'd be happy to join the discussion to talk about service mesh tracing as it relates to Linkerd. I indicated my interest in the document. Thanks!

Hi @xiaoerlyl -- linkerd is already setup to propagate context from any tracing system. For http traffic, context is usually passed via http request headers, and linkerd will forward those...

I'm not sure I follow this. Should the example request be `GET /book/api/published HTTP/1.1`? Instead of `GET /book HTTP/1.1`?