On Mon, Oct 10, 2011 at 10:37 AM, Raymond Feng <enjoyj...@gmail.com> wrote:
> Hi,
> Before the changes, we use jabsorb as the jsonrpc 1.0 implementation. I
> decided to use a home grown for number of reasons:
> 1) The jsonrpc protocol is simple enough. I'm trying to avoid the dependency
> to a non-active 3rd party project
> 2) I'm trying to leverage Jackson to improve performance
> 3) I want to use JSONRPC 2.0 at some point for binding.sca remoting
> 4) I want to try gzip encoding for some situations
Great, let me pickup the compression support.
Also, I noticed that there seems to be some issues with the current
response, which seems to always send error ? Per the 2.0 spec, error
should only be sent if there is an error. I'll investigate this issue
as well. Below is what I see while running the JSON-RPC tests.
Response as null:{"id":1,"result":"echo: Hello JSON-RPC","error":null}
[1] http://jsonrpc.org/spec.html
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
