paradigms
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| paradigms [2007/09/17 20:42] – niloo59 | paradigms [2007/09/18 18:46] (current) – niloo59 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Concurrency paradigms ====== | ||
| + | ===== Parallel Programming Models and Paradigms ===== | ||
| + | http:// | ||
| ===== Shared variables ===== | ===== Shared variables ===== | ||
| Line 5: | Line 8: | ||
| E.W. Dijkstra. [[http:// | E.W. Dijkstra. [[http:// | ||
| - | Languages that exploit shared variables include Java. | + | Languages that exploit shared variables include |
| Line 26: | Line 29: | ||
| ===== Concurrent constraint programming ===== | ===== Concurrent constraint programming ===== | ||
| + | |||
| An example of a language that exploits this paradigm is //ccp// - concurrent constraint programming language. | An example of a language that exploits this paradigm is //ccp// - concurrent constraint programming language. | ||
| Line 33: | Line 37: | ||
| [[http:// | [[http:// | ||
| - | |||
| - | |||
| One extension of this language has also been introduced with temporal/ | One extension of this language has also been introduced with temporal/ | ||
| Line 41: | Line 43: | ||
| A Timed Concurrent Constraint Language - DOI: http:// | A Timed Concurrent Constraint Language - DOI: http:// | ||
| + | |||
| + | |||
| + | |||
| Line 51: | Line 56: | ||
| Communications of the ACM(1992), | Communications of the ACM(1992), | ||
| - | Design of a Linda Kernel using Causal Multicast | + | Wells, George. Coordination Languages: Back to the Future with Linda. Rhodes University. |
| - | http:// | + | http:// |
| + | |||
| + | |||
| + | [[http:// | ||
| ===== Actor Model ===== | ===== Actor Model ===== | ||
| Line 62: | Line 70: | ||
| - | ====== Promise pipelining | + | ===== Promise pipelining ===== |
| Promise refers to an object that acts as a proxy for a result that is initially not known, usually because the computation of its value has not yet completed. | Promise refers to an object that acts as a proxy for a result that is initially not known, usually because the computation of its value has not yet completed. | ||
| - | Languages also supporting promise pipelining include: Joule and E | + | It was introduced in 1977 in a paper by Henry Baker and Carl Hewitt: Laws for Communicating Parallel Processes. |
| + | |||
| + | Languages also supporting promise pipelining include: | ||
| + | [[http:// | ||
paradigms.1190061757.txt.gz · Last modified: by niloo59
