> Tough call on breaking the backwards compatibility. There are a lot of folks > out there with deployed async methods that would not appreciate breakage. Well, it would only affect C++ and Erlang servers built with Thrift prior to r761389.
> I wonder if we could mitigate things by making people specifically compile > client-code with an option to send ONEWAY instead of CALL That sounds like a good way to go about it.
