This improves the API, by ensuring that JSON vs non-JSON responses have a
different method name and thus that the semantics don't depend upon the
implicit conversions to JSON::Value (or not). That confusion was leading
to several places where the content-type was wrong, and worse, when an API
was improved to use a UTF8String instead of an ASCII string, it would
suddenly send it as a JSON object instead of the string itself.
This is a pure internal API change, with the users of the API updated for
the new semantics.
This improves the API, by ensuring that JSON vs non-JSON responses have a different method name and thus that the semantics don't depend upon the implicit conversions to JSON::Value (or not). That confusion was leading to several places where the content-type was wrong, and worse, when an API was improved to use a UTF8String instead of an ASCII string, it would suddenly send it as a JSON object instead of the string itself.
This is a pure internal API change, with the users of the API updated for the new semantics.