Tuple Spaces (or, Good Ideas Don’t Always Win)
software-carpentry.org
Tuple Spaces (or, Good Ideas Don’t Always Win)
1–10 of 23 posts
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#2I've used this pattern with F# and Mailboxes, works great. Never knew it was called a Tuple Space.
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#3I did Linda in the university, during the Concurrent Programming course. It was lots of fun, even though we never actually wrote a line of code in any place other than the blackboard... It is sad that the model did not take off.
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#4I tried it in Ruby in ~2006, and found that many operations in Rinda were O(n) in the size of the tuple space :(
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#5I tried it in Ruby in ~2006, and found that many operations in Rinda were O(n) in the size of the tuple space :(
Interesting. Could a better-than-O(n) parallelisable tuple space be implemented with something like skip lists?
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#6Tuple spaces seem to have morphed into routers and filters for message queue protocols.
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#7Biggest issue I had was the idea of communicating data through the actual space which is why message based protocols that handle direct function/method invocation on take are so much easier to deal with and not worry about performance issues.
It sure as shot was fun to play with it in a big enterprise environment for a while though. =)
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#8Btw, Linda's name was "inspired" by Ada. Except instead of using a famous female mathematician (Ada Lovelace), he used a famous female pornstar (Linda Lovelace): http://en.wikipedia.org/wiki/Linda_Lovelace
Edit: Reference: http://c2.com/cgi/wiki?LindaEtymology
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#9Has anyone successfully used this for anything significant? As I post this there's only a couple of people posting about how either they tried but it didn't work out well enough, or they just played with it in school without any code.
It strikes me as having the same problems as RDF storage; precisely because the model is so general, there's nothing for optimizations to grab on to and optimize on. Your database has to stand ready to do anything equally. The core of database optimization is, when you really get down to it, working out how to tell your database which things you really want and what you will never care about, as in "This table has twenty columns but I will only query on name and phone number". In practice, limitations aren't always just there because of a lack of imagination or insufficient computer science education (though that does happen), sometimes they're there because you can't get any performance without them.
Re: Tuple Spaces (or, Good Ideas Don’t Always Win)
#10We use GigaSpaces (a commercial implementation of JavaSpaces that can also be used from a .NET environment) where I work, but we're underutilizing its capabilities terribly. The product itself apparently has a healthy niche in the financial services sector.