COMP10052-AAAF-06-2010-for-viewing

The server socket then simply goes back to listen for

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: r\n") # send Gopher message while True: buf = s.recv(2048) # chunk-read Gopher response if not len(buf): # stop when buf received nothing break sys.stdout.write(buf) # write each chunk onto stdout sys.exit(0) Server ­Side Sockets (1) 12           A “server” socket behaves more like a dispatcher. A “server” socket does not normally send or receive any data: typically, it simply listens for connec=ons on the host and port it (i.e., the “server” socket) is bound to. When it gets one connec=on, it also gets a new socket in response to that event. It then typically spawns a handler process, or thread, who is the one that actually uses the new socket to exchange messages with the client ­connected socket. The “server” socket then simply goes back to listen for more connec=ons. Server ­Side Sockets (2) 13   The “server” socket set ­up stage has more steps, as follows:         Create the “server” socket...
View Full Document

This document was uploaded on 02/10/2014.

Ask a homework question - tutors are online