This post originated from an RSS feed registered with Java Buzz
by Talip Ozturk.
Original Post: On JavaSpaces iterator and multi-read-write-take operations
Feed Title: Shared Memory
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: about java, jini, javaspaces, programming, aop and a little bit of me and life.
Description: According to JavaSpaces spec., you can only read/write/take one entry at a time. There is no specification-forced way of reading/writing/taking/paging multiple entries. I always thought JavaSpaces interface should support reading/writing/taking multiple entries until I read this email. It clearly explains why iterators and multi-read-write-takes are avoided in JavaSpaces spec.
Abstract: The argument over iterators in tuple-based systems is not a new one, however there are good reasons to resist adding them: first and foremost is semantic consistency. Here is a bit from Gelernter on the subject (while this paragraph obviously describes Linda, if you substitute "take" for "in", "entry" for "tuple" and "space" for "tuple space" you have JavaSpaces):
Previous Topic
