Why,
Now I have to rewrite any service where I use the Transaction API so that
the JavaSpace can own it. Oh while I am at it all my Leases out the door, I
cant even use the Entry as a lookup mechanism to find my UIDescriptors.
Why don't you just (re)create something called Linda
change Entry to Tuple, call it mmcgrady.local.Linda
heres you interface
package mmcgrady.local;
public interface Linda {
/// local linda v .00001
void write(Tuple tuple, LocalTransaction txn, long lifespan);
Tuple read(Tuple tmpl, LocalTransaction txn, long waitTime);
Tuple readIfExists(Tuple tmpl, LocalTransaction, long waitTime);
Tuple take(Tuple tmpl, LocalTransaction, long waitTime);
Tuple takeIfExists(Tuple tmpl, LocalTransaction, long waitTime);
void notify(Tuple tmpl, EventListener listener);
}
You would accomplish your mission faster that way rather than requiring the
entire Jini core to be unraveled so that you could have your way of a space
centric environment!
John Sarman
On Mon, Dec 22, 2008 at 7:09 AM, Michael McGrady <
mmcgr...@topiatechnology.com> wrote:
>
> 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
>
>
>
>
>
