> for bidirectional communications and for higher speed we think about
> removing HTTP overhead and speak JSON-RPC over TCP sockets.
yes, that's reasonable ;).
by the way, I've written a very modular json-rpc (v1.0 + v2.0) implementation
in python, which works over TCP, unix domain sockets and probably with any
other transport.
I'm planning to release it soon, but if you would like to see it before,
tell me, and I'll send you the code.
> The problem is to find anything of this transport in the latest JSON-
> RPC 2.0 spec. They even seems to have dropped a lot of infomations available
> in the older 1.0 documents, Or I'm just unable to find them. Is ther any
> reliable source for JSON specs. ?
the json-rpc specification and its transports are independent.
json-rpc should work with *any* transport: simple tunnel your
json-rpc-string through your preferred transport.
this is extremely easy for sockets. for HTTP, there are some suggestions
in the following proposal (although this proposal seems not to be up to
date concerning the json-rpc spec):
http://groups.google.com/group/json-rpc/web/json-rpc-over-http
regards,
Roland
I'm getting in on this thread late... I've created a JSON-RPC
implementation for Zend Framework that supports 1.0 and 2.0 already; it
currently works over HTTP, but it would be trivial to create
request/response objects for other environments.
It's stable, though it hasn't been released in a stable version of ZF
yet. You can grab it from the current 1.6.0RC3 package, or current ZF
SVN trunk.
Feel free to ping me if you have any questions.
--
Matthew Weier O'Phinney
mweiero...@gmail.com
http://weierophinney.net/matthew/
Thanks a lot,
hwinkel