Jan Algermissen wrote: > There are no other operations or invocations or whatever you call it. > > If you need to get stuff done, you do it by manipulating object > state, not by calling methods. > > Honestly, why is this so hard to get across?
Jan, the issue, for me, is that "calling methods" can manipulate object state just as readily as "opening URIs". So trying to say that you don't call methods any more is, for me, a rediculous argument to make in the "What is REST" argument. What is at issue is the level of abstraction that you're willing to have in place vs what you might perceive as "least necessary". If I can create a virtualization layer that involves "calling methods" and the result is exactly the same logic that one might code to open a URI, post some data and read a response, then what difference does it make that I'm calling methods to allow the abstraction to be made so that I'm not dependent on having to change the parameterization of a POST in multiple places where I need to make that call? You can say "manipulating state" and feel good about it. But, there's not a magic wand in any REST kit that I've seen. So, somewhere there's going to be code. Some of that code is going to "call methods" and some of that logic in those methods is going to "manipulate state". Why is that not a RESTful thing to do? Gregg Wonderly
