On 8/16/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
In terms of the basic transport, in M1 we had a JSON-RPC binding that supported JSON encoded data over HTTP. We have not got around yet to porting that to the new structure in the trunk. Looking at that would be a good way to dig into how Tuscany works.
I can make an attempt to try and port the jsonrpc binding from M1 over to trunk style extensions if this would be appreciated. I agree that should help me get an understanding of how some of Tuscany works.
Oisin may have been referring to how REST would impact the programming model rather than the implementation of bindings. For example, how would cache information in the request be handled by the binding and/or exposed to the application code? What is the mapping between REST resources and SCA services?
Yes, the more I read, the more I wonder if trying to support REST style web applications in SCA is going to become a square peg in a round hole problem. I've only begun really looking at this though, and welcome any thoughts on the subject of how one might attempt to interface REST resources in SCA. -Bert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
