Alexander Johannesen wrote: > > > On Jan 7, 2008 3:25 AM, Patrick May <[EMAIL PROTECTED] > <mailto:pjm%40spe.com>> > wrote: > > I went into more detail in my other message, but the short version is > > that, with Jini, I can implement my services in such a way that they > > transparently execute in the same process space as the client. You > > can't do that with REST. > > It's a big statement, for sure. Now I must ask, what does it mean to > run something in "the same process space as the client"? >
The feature of Jini that Patrick is referring to is, I believe, the use of mobile code and the fact that a service in Jini is simply a java object through which the functionality of that service is accessed by invoking normal java methods. (Whether those calls trigger any form of remote or inter-process communication is 'transparent' to the invoker). I don't think it makes sense to compare this feature either to REST as a style or to any implementation of it (e.g. HTTP). It seems to be outside the scope that REST addresses and therefore potentially orthognal. A more useful comparison might be between the use of RESTful HTTP versus the use of JERI. --Gordon
