Talk:State (computer science)
|WikiProject Computer science|
Merge with Program state?
|The content of Program state was merged into State (computer science) on 31 August 2012 . That page now redirects here. For the contribution history and old versions of the redirected page, please see ; for the discussion at that location, see its talk page.|
Broaden the definition
The present definition of 'state' was taken from a book on the design of digital systems. It is too narrow: it mostly applies when designing systems, hardly when studying existing ones, and it is limited to particular kinds of systems. The term 'state' is applied much more broadly, even in computer science. Rp (talk) 07:33, 16 August 2012 (UTC)
Improve the explanation?
I want to know about running state and waiting state ,such type of states.
I want to know what the virtues of stateless systems may be, as they are NOT obvious. They appear to be necessitated (?) by asynchronous systems, which begs the question "What are the merits of asynchronous communication"? Maximizing vastly redundant data transmission would appear to be one possible goal, admirably achieved. Until the web, all compuiter systems were stateful (and useful). The web is neither. Can anyone explain why the web is such a "dumb" interface? Was the intention to emulate "dumbest terminal imaginable" functionality, as this is what has occurred? —Preceding unsigned comment added by 220.127.116.11 (talk) 18:32, 3 September 2008 (UTC)
- I agree that it would be appropriate to answer these questions in this article:
- The discussion of simple states (e.g. 'on' vs. 'off', 'running' vs. 'waiting' vs. 'inactive', etc.) can be used to introduce the subject or give an example. The definition of state given now makes technical sense but doesn't really reflect how we usually think of state, and there is a technical reason for that.
- Stateful vs. stateless system descriptions: the point of statelessness is not to eliminate state from the system, but to make the system's *behavior* (interaction with its environment) independent from *hidden* state: no side effects, any information that may influence the outcome of an operation must be specified explicitly as input, and any effect must be explicit output. This makes systems easier to design and test, even more so when there is concurrency. However, this article may not be the most suitable one for discussing this at length. Rp (talk) 17:02, 29 September 2014 (UTC)
- Yes, there is also the article Stateless protocol which might be appropriate for some of it. I don't mind the additions, but the very important basic concept of state as the stored data set available to a program or logic circuit needs to be clear as the primary definition for nontechnical readers. --ChetvornoTALK 17:23, 29 September 2014 (UTC)