Re: receiving POST encoded in JSON

Scott,

Thanks for the additional information. I was so stunned by Kevin's report
of performance differences between your service program and that of Mihael
Schmidt; I was looking for an explanation. Unfortunately, I'm not well
versed in either; I haven't had a requirement to "consume" JSON under IBM i
yet. I'm interested in the topic, however.

I agree that "applications" typically know the format of JSON documents in
advance. An API that makes it easy to "find" the content you're looking for
is intuitive in that case.

I've been toying with writing a JavaScript utility that "merges" HTML
templates with JSON objects, where neither the format of the HTML nor the
JSON would be known in advance. I suppose that may have triggered the idea
of a similar use case under IBM i, though that is just an abstract notion
at this point.

I view the topic of JSON to be relevant to the topic of single-page
applications, client-side frameworkd, and possibly server-side web-service
frameworks, which we have been discussing during the past few weeks.