Comment 6 for bug 1175808

Added Heat, as you can see from the qpid JIRA I've already been down the path of investigating this, and came to the conclusion (for the Heat use-case at least) that the best option was *not* to JSON encode, since the recursive map serialization works OK for the data we typically need to pass (where none of individual the dict/map values contain strings >65535 but the JSON encoded entire template can easily be)

If there is a transparent workaround in oslo then we should sync that into Heat, as it's still possible users could encounter this limitation if they put particularly huge strings into a Heat template.

bug #1072917 has further details on my previous investigation into this.