[
Lists Home |
Date Index |
Thread Index
]
>* SOAP has no predefined method for "get the representation of a
resource". Every web service does it in a different manner, using its
own
>method name and its own addressing model. Of course the same goes for
"put the representation of a resource." This lack of standardization is
a >violation of the REST constraint that interfaces should be generic
and standardized.
Does this criteria imply that all REST component methods must define
standardized API's prior to deployment?
Or does it imply that REST developers must follow anyone that leads?
How does this account for interface versioning if the interface contract
is static (read: standardized)?
How do developers use the interface with assurance that it will not
change?
How does REST handle multiple interfaces to the same resource?
How does REST propose to extend interfaces?
Does REST's constraints extend into data types and consistency across
interfaces?
I am not a SOAP or REST proponent, I am simply trying to understand the
issues at large. Personally, I would prefer a URI-based trigger
protocol, rather than wrapper-style, but I have questions.
Sincerely,
Andrew Dubinsky
|
