Talk:Consistency model

Computing: CompSci Start‑class Low‑importance

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing

Start

This article has been rated as Start-class on Wikipedia's content assessment scale.

Low

This article has been rated as Low-importance on the project's importance scale.

This article is supported by WikiProject Computer science (assessed as Mid-importance).

This article is supported by Computer hardware task force (assessed as Mid-importance).

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Welch and Tanenbaum sources

I notice that the external link to lecture notes suggest that they are copyright Ian Welch 2004. However, the slides bear a striking resemblance to Andrew Tanenbaum's slides that accompany Chapter 6 of his Distributed Systems book[1]. I'm not sure of the policy regarding this. Any thoughts? Tim Watson 18:18, 24 January 2006 (UTC)[reply]

Programmer's rules

What are these "rules" that a programmer must follow to maintain consistency? —Preceding unsigned comment added by 128.138.64.20 (talk) 05:45, 27 February 2008 (UTC)[reply]

Confusion

The article says "To hold the contract, compilers may reorder some memory instructions". It is widely known that the reverse is true: the compiler may reorder instructions to optimize the code, but in some cases to ensure consistency this must be prevented (by usage of locking constructs or optimization barriers). I'm not sure if the author meant something else, or if this is plain confusion. --Blaisorblade (talk) 05:31, 26 December 2008 (UTC)[reply]

I was confused by that as well. I don't think consistency is an issue in those languages, because it is assumed that there is only one copy of data that gets stored in memory. If I understand the term "consistent" correctly, the issue applies only when there are multiple copies of the same data. BTW, if that's a correct statement, some version of it should appear in this article. Danielx (talk) 09:04, 18 October 2009 (UTC)[reply]

Begs the question

Instead of defining it, the first paragraph begs the question. Please add a definition of the concept to the first sentence.