7stud bbxx789_05ss at yahoo.com
Tue Feb 26 04:53:24 EST 2008

• Previous message (by thread): network programming: how does s.accept() work?
• Next message (by thread): network programming: how does s.accept() work?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Feb 25, 10:08 pm, Steve Holden <st... at holdenweb.com> wrote:
> There can be many TCP connections to a server all using the same
> endpoint. Take a look at the traffic coming out of any busy web server:
> everything that comes out of the same server comes from port 80. That
> doesn't stop it listening for more connections on port 80.
>

---
When you surf the Web, say to http://www.google.com, your Web browser
is a client. The program you contact at Google is a server. When a
server is run, it sets up business at a certain port, say 80 in the
Web case. It then waits for clients to contact it. When a client does
so, the server will usually assign a new port, say 56399, specifically
for communication with that client, and then resume watching port 80
for new requests.
---
http://heather.cs.ucdavis.edu/~matloff/Python/PyNet.pdf

---

• Previous message (by thread): network programming: how does s.accept() work?
• Next message (by thread): network programming: how does s.accept() work?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list