On Tue, Oct 6, 2009 at 5:38 PM, Luciano Resende <[email protected]> wrote: > On Tue, Oct 6, 2009 at 2:12 AM, ant elder <[email protected]> wrote: >> 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 >> > > Although I like the idea of having the binding-http supporting > wireformats and operation selection to allow returning resources in > different formats (e.g json, html, xml, etc)...and have this on my > list of todos... this wouldn't solve the problem, right ? We still > need a extension point to allow plug a "HTTP Client", which in most of > cases will be the Commons HTTP one we are using, but when in AppEngine > we would want a different one (single threaded based purely on > URLOpenConnection) >
You should be able to configure HTTP Client to not use multiple threads, have you looked at the HTTP Client doc? And we could control that configuration by defining tuscany specific attributes on http binding. I'm happy to help with the new http binding, would you like to work on it together? ...ant
