Asim Aslam

You're sort of arguing points I've argued before but I found gRPC became the sort of defacto standard wire format for RPC and if thats what go-micro is maybe it...

https://github.com/google/tarpc ``` tarpc differentiates itself from other RPC frameworks by defining the schema in code, rather than in a separate language such as .proto. This means there's no separate compilation...

Its not about using tarpc, its about taking the idea of having something defined without the use of proto

We need to make a decision on this. @xpunch I'm thinking we strip Publish from Client and Subscribe from Server. Rip out the mucp implementation and transport package. Default to...

@xpunch what do you think?

I think what @xpunch is trying to say is the model differs here. We treat grpc services as handlers and the service name could differ. With grpc you still have...

Well if you have some ideas, feel free to show us example code of how it would work without breaking backwards compatibility

v1 is not supported. Use v2, v3 or v4.

No this is just a mistake.

Then use v2. Go Micro v3-v4 has no API.