Re: Separate concepts for "service" and "targetResource?" (was RE : /service/@targetResource ?)

On Thu, May 22, 2003 at 09:56:55AM -0400, Walden Mathews wrote:
> That's true, but is one target going to be enough, or will the
> spec have to accommodate arbitrarily many targets?  Consider
> the transfer service that affects two accounts.

Hey, not my problem!  So long as the semantics of a RESTful resource
identifier aren't overloaded with WSDL goop, I'm happy.

(plus that the word "resource" not be used to name this attribute,
since not all resources are valid targets)

> And then if it is going to support many, then their roles have to
> be specified, and so on.....Burdensome and stiff.

You betcha!

MB
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis
  Actively seeking contract work or employment

Received on Thursday, 22 May 2003 10:15:41 UTC