On May 10, 2011, at 9:12 PM, Steve Vinoski <vinoski@ieee.org> wrote:

To be most flexible, any JSON-RPC 2.0 handler should be prepared to
take either a JavaScript array or a JavaScript object as its params
argument. See section 4.2 of the JSON-RPC 2.0 spec
(http://groups.google.com/group/json-rpc/web/json-rpc-2-0). An array
is represented in Erlang as {array, [...]} while an object is {struct,
[{key1, value1}, ...]}.

It's certainly true that a JSON array will have the {array, [...]} syntax.  My only point was that the signature on the callback has changed, such that the argument list is now represented as a JSON array, as opposed to a list of JSON objects, as it was before, even if none of the arguments you pass down to the (client-side) JSON layer are arrays.  I'm fine with the change; I'm just saying the signature change on the Yaws API should be noted.