Difference between revisions of "Sven/Notes"
From Organic Design wiki
m |
|||
Line 2: | Line 2: | ||
Topics: | Topics: | ||
==[[W:Client-server|Client Server]] model== | ==[[W:Client-server|Client Server]] model== | ||
− | How a client side [[W:Web browser|web browser]] interacts with a [[W:Web server|web server]]. See | + | How a client side [[W:Web browser|web browser]] interacts with a [[W:Web server|web server]]. See http://web-sniffer.net for an example of how http headers interact |
between the server and client. The [[W:Apache HTTP Server|Apache HTTP Server]] uses a listener process on [[W:Hypertext Transfer Protocol|port 80]] (and ports 21, 443) | between the server and client. The [[W:Apache HTTP Server|Apache HTTP Server]] uses a listener process on [[W:Hypertext Transfer Protocol|port 80]] (and ports 21, 443) | ||
to communicate with the client using the [[W:Transmission Control Protocol|Transmission Control Protocol]] [[W:Internet protocol suite|TCP/IP]]. The listener uses [[W:Thread (computer science)|threads]] to [[W:Fork (operating system)|fork]] child processes as client requests demand content from the web server. | to communicate with the client using the [[W:Transmission Control Protocol|Transmission Control Protocol]] [[W:Internet protocol suite|TCP/IP]]. The listener uses [[W:Thread (computer science)|threads]] to [[W:Fork (operating system)|fork]] child processes as client requests demand content from the web server. |
Revision as of 09:04, 30 March 2007
Contents
30 March 2007
Topics:
Client Server model
How a client side web browser interacts with a web server. See http://web-sniffer.net for an example of how http headers interact between the server and client. The Apache HTTP Server uses a listener process on port 80 (and ports 21, 443) to communicate with the client using the Transmission Control Protocol TCP/IP. The listener uses threads to fork child processes as client requests demand content from the web server.