Re: [RFC PATCH 08/11] trace-cmd: Apply the trace-msg protocol forcommunication between a server and clients

[Steven Rostedt]

On Mon, 19 Aug 2013 18:46:39 +0900
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@xxxxxxxxxxx> wrote:


> This message protocol is incompatible with the previous unstructured message
> protocol. So, if an old(new)-version client tries to connect to an
> new(old)-version server, the operation should be stopped.
> 

I'm a stickler for backward compatibility. I'm all for extensions.

I know this will just complicate things, but I don't mind that. What
should happen is, it should try to connect with the new protocol, if it
fails due to an older server, then it needs to fall back to the older
method, without the added features. We can freeze the older method if
need be. But I will not let a newer trace-cmd become incompatible with
an older version. I worked hard to keep it that way. There's only a few
exceptions to that.

Note, an older client needs to also work as is with a newer server.

Anyway, the old way only needs to stay the same, it does not need added
features. For that, a switch to the new way is needed.

If you need help in accomplishing this, I'll work with you on that.

Thanks!

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/