On Dec 21, 2008, at 5:10 AM, Niclas Hedhman wrote:
Apache River Lease
Apache River Transaction
Apache River Entry
Apache River JavaSpaces
Apache River Jini Service Platform
In Architectural Terms (since you are keen on talking about that),
this is what we already have. From a packaging and codebase
organizational point of view, it is not separated at the moment, but
is something that I would like to see happening.
Cheers
Niclas
Something like the following is what I would suggest, although there
are probably better alternatives that can be suggested.
apache.river.javaspaces.JavaSpace
apache.river.javaspaces.Lease
apache.river.javaspaces.Transaction
apache.river.javaspaces.Entry
apache.river.jini (service platform)
This is the actual API structure I find as of revision 728652.:
net.jini.core.constraint
net.jini.core.discovery
net.jini.core.entry
net.jini.core.event
net.jini.core.lease
net.jini.core.lookup
net.jini.core.transaction
net.jini.constraint
net.jini.discovery
net.jini.entry
net.jini.event
net.jini.lease
net.jini.lookup
net.jini.space
