AGL Framework - JSON responses 64K or over hang the binding
Description
Environment
Activity
Walt Miner December 8, 2017 at 8:55 PM
Close for EE RC4
Walt Miner November 3, 2017 at 10:19 PM
Closing as part of EE RC2

Jose Bollo October 23, 2017 at 12:49 PM
I agree with Matt that echoing messages would be helpful and needed.
However I'm embarrassed to achieve it at this time because the error is detected at a very low-level piece of code in the software stack. Adding a message here like a ERROR/WARNING/NOTICE (WARNING is the most appropriate because it is not an error to reject too big messages, quiet the opposite) implies many unpleasant things: definition of verbosity, use of syslog or printf or ??. In my opinion, the correct solution is to handle it at upper layers (already possible but not implemented). That require more work and I postpone it to later, sorry.
Question: act that it is solved and create an other issue for reporting messages? or keep this one unsolved?

Jose Bollo October 23, 2017 at 10:45 AM
Thank you for your quick answer, I'll push the resolution today.
About reporting the error, I'll try but it is a low-level error that have to be reported at high level...

Matt Ranostay October 23, 2017 at 9:29 AM
I'd guess for now I'd never suspect over 1M but it would be nice even if hits the limit to not hang and report back
64k and over JSON responses hang the afm binder framework.. this currently happens because of album art being passed in over that limit in base64.
Doesn't seems to be JSON-C library based since that function completes but hangs once the afb_req_success() function gets the json response data.