Talk:Tuple space

message: Shouldn't this artlce be under "Tuple space" not "Tuple spaces"?  Either way, I suggest a redirect be created from the other one.
:As far as I know it is only used in plural from. Hence, it should be Tuple Spaces. Creating a redirect is a good thing of course. Koffieyahoo 12:07, 19 August 2005 (UTC)
replies: text: The following discussion is an archived debate of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section. 
The result of the debate was merge both.--Jorfer 16:23, 12 June 2007 (UTC)
thread_title: Plural

message: Seems like a good idea. However, it would propose to merge the JavaSpaces example to that article and add a pseudo code based example here. -- Koffieyahoo 03:11, 17 July 2006 (UTC)
replies: text: Well, I don't REALLY know much about this stuff but it seems to me that "Tuple space" is a more general idea that Object Space falls under and JavaSpaces utilizes.  Though Tuple space is the weakest article of the three, I think merging the two articles into it would create a better picture of the concept and also serve to concentrate further expansion on the subject.  I vote YES to merging all of the articles into "Tuple space."  -- Nanobri 3:36, 6 June 2007 (UTC)
thread_title: On the proposed merge

message: Are the try-catch blocks in the current Java example really necessary?  It seems to me that either
* no exception can be thrown by the try-block, in which case the catch-block is useless and confusing, and should be deleted; or else
* some exception could be thrown by the try-block, indicating an error, in which case it would be caught and ignored by the catch-block, silently introducing a bug.
If any of the operations in the Java example could actually throw exceptions, those exception types should be listed in a throw-specification, and in any case, the catch-block should be removed. If possible, someone with more Java experience than I should rewrite the code so that it cannot throw any exceptions in the first place. --Quuxplusone 05:30, 2 August 2007 (UTC)
thread_title:  Java example 

message: "Implementations of tuple spaces have also been developed for Smalltalk, Java (JavaSpaces), Python, Ruby, TCL, and Lisp."  It would be nice if pointers to all of the claimed implementations were provided.  The quoted sentence (as of this writing) only points to the Wikipedia pages for those six languages.  The "Implementations" section has five links, but doesn't say which links are for which language, nor which which of the languages are left out.  —Preceding unsigned comment added by Vrmlguy (talk • contribs) 12:41, 17 September 2007 (UTC)
thread_title:  Unsupported claims 

message: Tuple space is an example of DSM. Agree? If yes, I will put appriopriate links Szopen (talk) 14:08, 17 April 2008 (UTC)
thread_title:  DSM 

message: In the JavaSpaces section it says "JavaSpaces remains a niche technology mostly used in the financial services and telco industries where it continues to maintain a faithful following." It would be good to add more information and references to real-world examples of JavaSpaces. Robert (talk) 02:29, 27 April 2009 (UTC)
thread_title:  Real world applications 

message: This article was hijacked by the Object Oriented crowd: David Gelernter et al. developed the concept of a tuple space and the associated coordination language Linda (which are primitives added to a host sequential language), not of an "object space".
The silliness in this attempt to rewrite history is manifest in this passage from the "Object spaces" section: "Objects, when deposited in an Object Space are passive, i.e., their methods cannot be invoked while the objects are in the Object Space."
I tried to correct the article but the syntax-highlighted editor is so buggy that it continually mess with the editing process. I gave up.
—MaD70 (talk) 13:34, 17 September 2020 (UTC)
thread_title:  "Object Spaces" = rewriting history