Comments on: JSON and JSON-RPC for Erlang http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang What happens at LShift Sun, 07 Sep 2008 13:11:33 +0000 http://wordpress.org/?v=2.0.12-alpha by: tonyg http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-80746 Mon, 14 Jan 2008 11:41:51 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-80746 <p>Hi Daniel,</p> <p>It ought not to be too difficult. It may need a bit of refactoring. The key differences will be separating out the inets-httpd specific way of retrieving the URL, query parameters, and POST body from the HTTP request. The main entry point that inets-httpd uses (after a few trivial calls) is do_rpc/1, and the main workers are parse_jsonrpc/2 and invoke_service_method/6. See also the section "<a href="http://www.lshift.net/~tonyg/erlang-rfc4627/doc/mod_jsonrpc.html#invoking-erlang" rel="nofollow" rel="nofollow" rel="nofollow">Invoking JSON-RPC procedures from Erlang</a>" in the manual.</p> Hi Daniel,

It ought not to be too difficult. It may need a bit of refactoring. The key differences will be separating out the inets-httpd specific way of retrieving the URL, query parameters, and POST body from the HTTP request. The main entry point that inets-httpd uses (after a few trivial calls) is do_rpc/1, and the main workers are parse_jsonrpc/2 and invoke_service_method/6. See also the section “Invoking JSON-RPC procedures from Erlang” in the manual.

]]> by: Daniel Kwiecinski http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-79735 Tue, 08 Jan 2008 10:53:07 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-79735 <p>Hi,</p> <p>How easy would be to convert mod_json into yaws appmod? Could you make any suggestion - clues to make this task easier?</p> <p>Cheers, Daniel</p> Hi,

How easy would be to convert mod_json into yaws appmod? Could you make any suggestion - clues to make this task easier?

Cheers,
Daniel

]]> by: rich http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-68819 Tue, 23 Oct 2007 17:07:30 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-68819 <p>there's also <a href="http://www.erlang-projects.org/Public/news/ejson/" rel="nofollow">ejson</a></p> there’s also ejson

]]> by: Mikl Kurkov http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-67881 Thu, 11 Oct 2007 09:50:20 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-67881 <p>Hi! Thanks for very good work. I'm interested in your jsonrpc implementation. It seems to work pretty good. But I don't througly understand is it synchronyse or not. I mean if some rpc request takes long time to proceed will over requests wait for it or they can be proceed in parallel. As I can see in current implementation you use genserver:call so it is not possible to proceed other request until previous will proceed. Also with function call - all system will wait current call to return. Do you plan implementing async requests in this system. Or may be I misiing something.</p> Hi!
Thanks for very good work. I’m interested in your jsonrpc implementation. It seems to work pretty good. But I don’t througly understand is it synchronyse or not. I mean if some rpc request takes long time to proceed will over requests wait for it or they can be proceed in parallel.
As I can see in current implementation you use genserver:call so it is not possible to proceed other request until previous will proceed. Also with function call - all system will wait current call to return.
Do you plan implementing async requests in this system. Or may be I misiing something.

]]> by: Sam Ruby http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65838 Fri, 14 Sep 2007 13:01:48 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65838 <p>Email is required to post a comment, but even you can't see it?</p> <p>In any case, rubys at my weblog's host.</p> Email is required to post a comment, but even you can’t see it?

In any case, rubys at my weblog’s host.

]]> by: tonyg http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65355 Thu, 06 Sep 2007 09:40:26 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65355 <p>Sam, that's great stuff! Thank you. I'm very interested in integrating your utf-8 work - I'll get in touch via email.</p> <p>(Update: Er, or I would if I could find an email address for you! :-) I'll leave a comment on your blog, instead.)</p> Sam, that’s great stuff! Thank you. I’m very interested in integrating your utf-8 work - I’ll get in touch via email.

(Update: Er, or I would if I could find an email address for you! :-) I’ll leave a comment on your blog, instead.)

]]> by: Sam Ruby http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65325 Wed, 05 Sep 2007 17:26:53 +0000 http://www.lshift.net/blog/2007/02/17/json-and-json-rpc-for-erlang#comment-65325 <p>I'm interested in proving patches to support utf-8. For more background (and a link to the first patch), see <a href="http://intertwingly.net/blog/2007/09/05/Atom-to-JSON-with-Erlang" rel="nofollow">here</a>.</p> I’m interested in proving patches to support utf-8. For more background (and a link to the first patch), see here.

]]>