Mark Baker wrote: > On 3/22/07, Gregg Wonderly <[EMAIL PROTECTED] <mailto:gergg%40cox.net>> wrote: > > I think about it in terms of the data passed. With HTTP, you open a > port, with > > a particular transport. You send an operation string of the form > > <OPER> <RESOURCE>. You then follow that up with headers for http 1.1 > and later, > > a blank line, and then any associated content, which is specific to > the type of > > operation you are invoking. You then might wait for a reply depending > on what > > type of operation you invoked. > > > > With RMI, the client end point object opens a port using a configured > transport. > > The operation is uniformly and always "invoke". The resource is > indicated by > > sending the object id and method name, and the associated content, the > > parameters to the call, are sent. You always wait for a reply, and > operations > > continue. > > > > This is how I see it anyway. > > Ok, well it seems clear that you're using different terminology than > the rest of us in this conversation, as we see operation and method as > the same thing. But to put things in your terms, the uniform > interface constraint would mean that every service offered the same > set of *methods*. > > Does that help?
So are you drawing the line there to force it to be different or because it actually is different. I'd argue that if HTTP is "the appplication protocol" then "RMI is the application protocol". Thus if GET, PUT, DELETE, POST are the HTTP operations, then RMI's INVOKE is the operation, and it is uniform in the same way. How come you would consider that to not be the case? For any particular RMI client to talk to an RMI server, it is that INVOKE protocol that is at the root of their ability to interact. It is the HTTP protocol's implementation that is the uniformity that allows web clients to talk to web servers. So, it seems to me that you're considering RMI's invocation protocol to be at the same layer that TCP is for HTTPs implementation. My argument is that this is not the case. RMI is the application protocol. The methods invoked are the resources being used. Help me understand why I can't see it the way you are pressing for it to be understood. Gregg Wonderly
