Gregg, "invoke" is not a uniform interface because it doesn't work unless you also supply a method name to invoke. And in RMI, the method names are not uniform. They are getXXX and setXXX for each of the public attributes in the object, plus any other operations that the developer chooses to expose.
In REST, you also have the equivalent of "invoke", but the methods that you can invoke are always uniform. In the case of HTTP, they are GET, PUT, POST, DELETE. Anne On 2/27/07, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
Mark Baker wrote: > RMI is not uniform in the same way that the standard REST connector is > uniform. Perhaps you and/or Jan can provide a more descriptive refutation of the issue? I'm sorry that I can't see the difference. I'm trying to see the issues. I'm obviously missing the point. You say "invoke" is not an application layer operation. perhaps you can tell me how the application on the client will talk to the application on the server without using "invoke" to instruct it which resource to reference and what data to pass? If you can provide specific points of counter example that would help the most I think. Gregg Wonderly
