Stateless server definition
-
Hi, Everyone. Can someone describe me what is the "stateless server"? My thoughts (I still want to get an explanation about the term above): I asked google[^]. The best definition I found is "A stateless server considers each page request independently". So, I think, the main accent is that the stateless server doesn't do any differences between users' requests. It thinks like every request is a new, from a new user. Let's imagine a google search server that only search functionality, a very-very simple search functionality: just go to an "indexed sites DB" for results. Is that one a stateless? I think -- yes. Because it doesn't bother itself with questions: "Is that user a new, what he did last time,...". It just parses the request, goes to the DB and answers. It uses no information about last requests, so "considers each page request independently". Am I right? Thanks, Aikin
-
Hi, Everyone. Can someone describe me what is the "stateless server"? My thoughts (I still want to get an explanation about the term above): I asked google[^]. The best definition I found is "A stateless server considers each page request independently". So, I think, the main accent is that the stateless server doesn't do any differences between users' requests. It thinks like every request is a new, from a new user. Let's imagine a google search server that only search functionality, a very-very simple search functionality: just go to an "indexed sites DB" for results. Is that one a stateless? I think -- yes. Because it doesn't bother itself with questions: "Is that user a new, what he did last time,...". It just parses the request, goes to the DB and answers. It uses no information about last requests, so "considers each page request independently". Am I right? Thanks, Aikin
-
Hi, Everyone. Can someone describe me what is the "stateless server"? My thoughts (I still want to get an explanation about the term above): I asked google[^]. The best definition I found is "A stateless server considers each page request independently". So, I think, the main accent is that the stateless server doesn't do any differences between users' requests. It thinks like every request is a new, from a new user. Let's imagine a google search server that only search functionality, a very-very simple search functionality: just go to an "indexed sites DB" for results. Is that one a stateless? I think -- yes. Because it doesn't bother itself with questions: "Is that user a new, what he did last time,...". It just parses the request, goes to the DB and answers. It uses no information about last requests, so "considers each page request independently". Am I right? Thanks, Aikin
-
-
I re-read the definition and found that this one is a definition for stateless, not for stateless server. I didn't saw that before. It is a very useful one. Thanks. But I don't think it is fully related to a "stateless server", because the one doesn't have it's own "persistent state". A server is a container for applications that are ran into the one. So It can only provide underlying applications with a more usable request to clients. Yes, it can store some information, but not for itself -- for it's applications. So, I think is better to use it's own definition: a stateless server[^] A stateless server is a server that treats each request as an independent transaction that is unrelated to any previous request. Although this definition is very useful to understand next ones: a stateless application, a stateless session, ... Thanks again, led mike.
-
I re-read the definition and found that this one is a definition for stateless, not for stateless server. I didn't saw that before. It is a very useful one. Thanks. But I don't think it is fully related to a "stateless server", because the one doesn't have it's own "persistent state". A server is a container for applications that are ran into the one. So It can only provide underlying applications with a more usable request to clients. Yes, it can store some information, but not for itself -- for it's applications. So, I think is better to use it's own definition: a stateless server[^] A stateless server is a server that treats each request as an independent transaction that is unrelated to any previous request. Although this definition is very useful to understand next ones: a stateless application, a stateless session, ... Thanks again, led mike.
AikinX wrote:
But I don't think it is fully related to a "stateless server"
It is definitely fully related. In the context of "a server" the definition of "stateless" does NOT change.
AikinX wrote:
A server is a container for applications that are ran into the one.
No. It can be but the word "server" is not limited to that. In client-server architecture "server" refers to the process that services the clients. However there is a non client-server architecture use of a server process that may not service clients at all. It may not receive requests of any kind.
led mike