aboutsummaryrefslogtreecommitdiff
path: root/content/share-memory-by-communicating.article
diff options
context:
space:
mode:
Diffstat (limited to 'content/share-memory-by-communicating.article')
-rw-r--r--content/share-memory-by-communicating.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/share-memory-by-communicating.article b/content/share-memory-by-communicating.article
index 12bff79..c254ea0 100644
--- a/content/share-memory-by-communicating.article
+++ b/content/share-memory-by-communicating.article
@@ -1,7 +1,7 @@
# Share Memory By Communicating
13 Jul 2010
Tags: concurrency, technical
-Summary: Traditional threading models (commonly used when writing Java, C++, and Python programs, for example) require the programmer to communicate between threads using shared memory. Typically, shared data structures are protected by locks, and threads will contend over those locks to access the data. In some cases, this is made easier by the use of thread-safe data structures such as Python's Queue.
+Summary: A preview of the new Go codelab, Share Memory by Communicating.
Andrew Gerrand