On Aug 16, 2006, at 11:51 AM, Bert Lamb wrote:
Hi Oisin,
I am still at the point where I am trying to get my head really
wrapped around how Tuscany works and how one would go about creating a
REST binding, so I'm afraid I'm not quite at the point where I am
capable of speaking very intelligently on the subject.
Have you put much thought towards the subject of a REST binding? Are
there things about which you believe we should be aware?
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.
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?
IMO we can tackle this in to stages. First one is to get the basic
transports working (like JSON-RPC, XML over messaging, HTML over HTTP
etc.); that would at least allow SCA applications to provide/access
REST resources. The second stage would be to support more of the
semantics of RESTful interactions.
Or, I may be talking garbage and would be happy to learn more :-)
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
