Concerning the how: Do you know in what data structure River does store the tuples? --Joerg
-----Original Message----- From: "Dan Creswell" <[email protected]> Sent: Thursday, February 21, 2013 6:50pm To: [email protected] Subject: Re: transient tuple space A bit of history: Jini (now River of course) went to great lengths to separate implementation details from service abstractions. That is the "how" was not nearly as important as the "what". "Do one thing well" was a phrase oft-quoted in respect of services. And so to JavaSpaces: The spec basically says that if the JavaSpace is a transient implementation, it will forget its contents at the time of exit (crash or normal). Persistent is the opposite, contents are remembered across exits (crash or normal subject to transactional constraints of course). Given the above, a transient space could actually make use of disk perhaps as an overflow for memory. Thus (b), below is to my mind the "correct" interpretation of the spec. On 21 February 2013 20:28, <[email protected]> wrote: > All, > > what is a transient mode/tuple space by definition. To me the documentation > is not quite clear whether it is > > a. an in memory tuple space that does not use slow disk space > > b. a tuple space that may or may not use disk space for storage but that is > in any case not preserved after a restart > > --Joerg > >
