Re: copy constructor for sockets

[Simon Wright <simon@pushface.org>]

"Andrew Carroll" <andrew@carroll-tech.net> writes:

> So, the server must accept the socket and do an initial read to get the
> header information (GET or POST) to know which type of task to create.
> Then I want to initialize the socket that is in the task type to be the
> same as the socket in the server that was just accepted.  It would
> probably need to be a "deep copy" of the socket because the server will
> need to release the socket and the task will need to keep the socket.
> By release I mean close() and by keep I mean use for communication.

You mustn't finally close() the socket you get back from the accept()
until you have sent your reply. The browser client is expecting you to
use it.

In C terms, you could dup() the socket, pass the result off to the
task, and close() the first socket, but it doesn't seem necessary here
-- might be a good idea when the thing that is going to talk over the
socket is a child process that you have fork()ed, so as to avoid a
file handle leak in the server process, but these are tasks so I don't
think that's likely to be a problem. Others will know more than I do
about this!

-- 
Simon Wright                               100% Ada, no bugs.