terminology - Stateless vs Stateful - I could use some concrete information -


I am interested in articles about which there is some concrete information about state-of-the-art and stateful design in programming. I'm interested because I want to know more about this, but in reality there can not be any good articles about it. I have read dozens of articles on the web that are obscurely discussing this topic, or they are talking about web servers and sessions - which are 'competitive state versus stateless, but in the coding of the characteristics of state versus state-of-the-art design Interested in Example: I have heard that BL-Class design is stateless by the unit sections (or at least, which I call them - such people (ID, name, ..)) are state-wise.

I think it is important to know, because I believe that if I can understand it then I can write a better code. (Eg granulity in mind). Anyway, / P>

Stateful (such as WinForms): stores data for more use, but limits the scalability of an application, because it is limited to the CPU or memory limit

Stateless (like ASP.NET) tries to defy ASP viewers): After the work is completed, the data is transferred, and the example is handed back to the pool pool (amorphous) are given.

As you can see, it is very vague and limited information (and a lot of focus on server interaction), so I'm really grateful if you can provide me some delicious bits of information :)

I'm su ggest that you start with stack overflow that discuss the benefits of stateless programming is. It is more in terms of functional programming, but whatever you read also applies to other programming criteria.

Stateless programming is related to the mathematical idea of ​​a function, which is called with the same logic, always return the same result, it is a major concept of functional programming paradigm and I hope that you Will find many relevant articles

Another area that you can research to understand more. These designs are "stateless", unlike other web technologies that try to keep the state in some way (in fact what do you say that ASP.Net NetVative is not correct - ASP.NET has given the state Have tried hard to use the viewstate, and of course it is marked as a stateless. On the other hand, ASP.NET MVC is a Statace Technology). There are many places that discuss "statelessness" of permanent web services (like blogspots), but you can start again with SO.

Comments