Hi David, On 7/10/06, David Forslund <[EMAIL PROTECTED]> wrote: > Mark, > I don't understand your answer. How does defining the operations > in "a document" make it any easier to deploy the application? One > has to agree on the semantics of the document to understand the > data and the operations. This is basically equivalent to a UML > model that must be sent over the single interface. (data + methods = > objects). > What semantics are used to express this? Greg's point is that one has to > do the same work in either case. The debate then over which is an easier > way to express the semantics (and then to implement them).
I'm not exactly sure what you're asking there, because you use "semantics" in a manner inconsistent with how I'd use it. But I don't understand how you can begrudge REST's ability to constrain that all interfaces be the same. I mean, feel free to believe that this constraint comes at a large cost if you must (e.g. makes the resulting system only good for transferring HTML to humans using browsers), but you can't say that REST doesn't do something it's *defined* to do. Mark. ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
