On Sun, Dec 21, 2008 at 12:33 AM, Michael McGrady <mmcgr...@topiatechnology.com> wrote: > The same is true of the architecture of the Web. Note that the > Internet is defined solely by documents of various protocols: TCP/IP, HTTP, > etc. Lookup is not included.
Go read RFC-2165 and all the related ones. Then come back and say that IETF is not concerned with Service Lookup. It is a different topic whether Jini should now use SLP or not, but AFAIU SLP wasn't around when the Jini team started out... I think that you are confused over the terminology used here. JavaSpaces' take() operation has nothing to do with lookup. JavaSpaces API-wise has dependency on; - Entry Specification - Transaction Specification - Lease Specification (maybe something else I forgot) And I agree with Dan, Gregg and others that this is architecturally sound. Even Structure-101 agrees to a large extent (there are some smaller mistake but nothing major). And I think that your argument is that the above are Jini specific specifications. They are developed by the Jini group, but most people here would define Jini as "Discovery, Lookup and Join", and the 3 above ones are 3 pre-requisites that doesn't/didn't exist. So, the argument at that level would be that these and other specs are much more generic than Jini itself. Then the fact that JavaSpaces implementation here uses Jini under the hood is not much stranger than 99.something% of all TCP implementations uses IP under the hood. So, architecturally speaking, I think you are on really thin ice, and that you are outright wrong about your assertions. Cheers Niclas
