On Tue, Oct 6, 2009 at 5:17 AM, Luciano Resende <[email protected]> wrote:
> - The JSON-RPC Binding is using Commons HTTP Client, which spawn > threads which is not allowed in the AppEngine environment. I have a > local version of the binding using only URLOpenConnection, but it > would be good if we could have a extension point and provide a way to > plug a alternative implementation that is single threaded. > What I think would be a good approach is to update the http binding for the draft http binding spec, implementing full support for wireformats, operation selectors, and customizable plug points, and then have the other http based bindings like jsonp and jsonrpc delegate to the http binding runtime code. So the <binding.jsonp> is just gets translated to a <binding.http> and whatever config attributes the http binding needs to support jsonp. ...ant
