Re: copy constructor for sockets

[tmoran@acm.org]

>> socket to the task during the rendezvous, and let the task create a socket
>> and do the socket-accept.
>I know you can use select() or poll() to block until an accept() would
>succeed, is that the idea?
  Yes.  Have the server task poll (frequently) to see if an accept() would
succeed, then rendezvous with the handler task which does the actual
accept().  Note the OP's Get_Line could take a very long time if the
caller is not a fast browser - a typist surfing with telnet www.x 80, say.
So having the server do the Get_Line allows such a single slow typist to
block all other new traffic.
  In this case, though, the server could start/call a task and not worry
about whether the task blocks on the accept().  If it does block, then
there's no browser calling and the server has nothing else to do anyway.
Eventually somebody surfs by, at which time the task hanging on the
accept() does the accept() and immediately finishes its rendezvous and the
server is allowed to go and prepare another acceptor task.
  The server is like a restaurant maitre d' - he should be minimizing
the time people wait at the door.  To do that he assigns them to a
waiter, who takes their drink order, tells them the daily specials, etc.
while the maitre d' turns his attention to the next customer in line.
  One more thing: if the server does the Get_Line, that suggests there's
only one Get_Line per accept(), ie, no persistent connections.