This one is for all the IT wizards out there. Can you explain what a server is in reasonable depth in words I can understand?
This one is for all the IT wizards out there. Can you explain what a server is in reasonable depth in words I can understand?
A server is a person who brings food to you.
A central computing resource that provides information to the computer from which you connect to said server.
I think it's just another fancy name for a website
Its a computer or a prigram that is accessed by other computers or programs called clients.
Example. Your browser is a client. It requests information from websites which are located on other computers (servers) that send the inforamtion back to you.
Simple.
malmo wrote:
Its a computer or a prigram that is accessed by other computers or programs called clients.
Example. Your browser is a client. It requests information from websites which are located on other computers (servers) that send the inforamtion back to you.
Simple.
Ok... Can you explain it to me like I'm two?
You, Horizon, are a client. A very special client. When a mommy loves a daddy very much they make little clents - just like you! Your mommy is a server. When you poop your pants you are requesting your mommy to change your diapers.
Siimple.
there can be several layers as well.
so for example when I make a post on letsrun, my browser (the client) sends the post request to the letsrun.com web server with what I want to post. The web server then writes that post to the letsrun.com database server where it will be stored.
Then when someone else opens the thread, their browser requests the page from the lrc web server which in turn requests it from the lrc database server. the web server formats the data and sends it back to the browser and they seem post.
other types of servers: chat servers, search servers, caching servers (in memory data), time servers (the client simply asks "what time is it?"), video, etc.
so we, the users of letsrun.com are the thousands of clients. we use our clients to talk with the 5 or so letsrun.com servers which store the posts, the formatting, and the logic surrounding letsrun.com.
biogen wrote:
and the logic surrounding letsrun.com.
0/10
A server is essentially a computer that runs 24/7.
Let's say you want to go to a website. You open up an internet browser, let's say Google Chrome. Then you type in the url address of the website you want to go to, let's
. So what does your computer do behind the scenes?
Basically your browser sends what's called a "Request" to the url address, and your browser receives a "Response". The Request is basically the content your browser wants in order to display the web page on your screen correctly. And, the Response is said content, which is dependent on what the Request is.
So let's pretend this whole process is like asking your friend to grab you a big mac from McDonald's down the street. The Request is the burger you want and how you want it (ie you may want it without lettuce and tomatoes or whatever). The url address is the address of the McDonald's your friend is going to. Once your friend gets to McDonald's and places your order, McDonald's prepares the food then gives (or "serves" if you will) the actual burger (which would be equivalent of the Response) to your friend, who drives back to your place and gives it to you.
In this example, a "Server" is the actual McDonald's that makes your burger how you want it. In the case that the McDonald's is a busy/popular one, it needs to make sure that it can handle large volumes of customers' requests correctly, quickly, and efficiently.
Hope that helps,
JP
Let's say you want to go to a website. You open up an internet browser, let's say Google Chrome. Then you type in the url address of the website you want to go to, let's say letsrun.com. So what does your computer do behind the scenes?
Basically your browser sends what's called a "Request" to the url address, and your browser receives a "Response". The Request is basically the content your browser wants in order to display the web page on your screen correctly. And, the Response is said content, which is dependent on what the Request is.
So let's pretend this whole process is like asking your friend to grab you a big mac from McDonald's down the street. The Request is the burger you want and how you want it (ie you may want it without lettuce and tomatoes or whatever). The url address is the address of the McDonald's your friend is going to. Once your friend gets to McDonald's and places your order, McDonald's prepares the food then gives (or "serves" if you will) the actual burger (which would be equivalent of the Response) to your friend, who drives back to your place and gives it to you.
In this example, a "Server" is the actual McDonald's that makes your burger how you want it. In the case that the McDonald's is a busy/popular one, it needs to make sure that it can handle large volumes of customers' requests correctly, quickly, and efficiently.
Hope that helps,
JP
Sorry didn't mean to embed the link...
oh yeah and in case it wasn't clear, a server is just another computer. that's all. it is a computer out there that sits there listening for requests from clients, which it then processes and responds.
Think of Rosamund Pike "Gone Girl" , as the Server . She is holding a box cutter. The Clients are the men lining up to get killed. Each time she kills a man , this is a server / client exchange. The more power Rosamund has, the more men she can kill. This is called network capacity.
JamesPardon wrote:
So let's pretend this whole process is like asking your friend to grab you a big mac from McDonald's down the street. ... McDonald's prepares the food then gives (or "serves" if you will) the actual burger (which would be equivalent of the Response) to your friend, who drives back to your place and gives it to you.
Hey, you forgot the cookie.
So, is the monitor a server to my retina?
A server is a big computer somewhere else that can talk to your computer or smart phone and send it information.
Because your computer or smartphone is small by comparison, and the server is gigantic, it has a lot of information your computer or phone doesn't have, and is happy to send it what you want when you ask for it.
A server is a NSA man-in-the-middle attack that spies on your every move, thanks to the Shockwave flaw that they snuck in to Bash shells.
This is how I learned what a server is: