Martin Taillefer

Some additional perspectives. Updating the dictionary is a relatively rare thing. Having the dictionary in the binaries, rather than read from a config file or some sort, means that updating...

I was thinking that in case of failure, mixerclient would fall back to the V1 global dictionary which is the baseline. It would continue to use V1 until it is...

We currently have stated as an objective to have 3 partners write adapters in the Q2 timeframe. Unfortunately, Beta is slated for end of August. It's annoying that we do...

Each template type needs a corresponding test suite. Ideally, this could be supplied by the template author.

RequestId is intended to capture the whole scope of an operation from the proxy's perspective. All the Check/Report calls made by the proxy on behalf of a single "event" would...

Yep, very true. Plumbing through the service name provide multi-service multi-tenancy. Plumbing through mesh id gives multi-mesh multi-tenancy support. Should we combine the mesh id and service name into a...

We discussed this and decided that we don't want the mesh id. Mixer is designed to operate within the context of a single mesh. It needs to support multi-tenancy between...

i'd rather extend instances instead of passing magic undiscoverable values in the context. Do you expect a problem with doing this? As for IstioService, that's an interesting question. We apply...

We should be using the patterned described here: https://blog.golang.org/context In particular, we need a NewContext/FromContext pattern. Adapters will call FromContext to get the payload. We used to have a custom...

I don't understand your #2 point. Can you restate? On Tue, Oct 24, 2017 at 10:04 AM, mandarjog wrote: > > 1. Mixer uses destination.service as the primary identifier which...