Re: copy constructor for sockets

[tmoran@acm.org]

>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.

Remember that a task is a thread of control, not a sequence of
instructions.  From that viewpoint, your server needs to fire up a
task/thread, and that thread needs to find out whether it should execute
the Get or the Put sequence of instructions.  You can pass the server
socket to the task during the rendezvous, and let the task create a socket
and do the socket-accept.  That lets the server get back to waiting for
calls as quickly as possible, while the task does the Get_Line (which
could potentially take a while) and calls an appropriate Handle_Get or
Handle_Post procedure.  You can see an example of this in Smplsrvr (part
of the free Claw download at www.rrsoftware.com).  You might also want to
see how AWS does it.

> Doesn't the ":=" operator to a "deep copy"?
If the object is Limited, ":=" is illegal.  (That's the case for Claw
Sockets.) If it's Controlled, then ":=" does a bit pattern copy followed
by a call on Adjust, which may do nothing, may modify pointers or
whatever, or may do a deep copy - whatever it wants.  If the object is not
Controlled, and isn't Limited, then ":=" just does a bitwise copy.