From: tmoran@acm.org
Subject: Re: copy constructor for sockets
Date: Sat, 22 May 2004 18:39:13 GMT
Date: 2004-05-22T18:39:13+00:00 [thread overview]
Message-ID: <l7Nrc.41912$gr.4073785@attbi_s52> (raw)
In-Reply-To: x7v3c5svfqc.fsf@smaug.pushface.org
What happens when one of the copies is "closed" and then someone "writes"
on the other? Or worse, is closed, then reopened with a different remote
connection. A socket is in some ways like a pointer to a (remote) data
object - it's always living dangerously to have multiple independent
pointers to the same object.
next prev parent reply other threads:[~2004-05-22 18:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 10:19 copy constructor for sockets Andrew Carroll
2004-05-22 11:55 ` Simon Wright
2004-05-22 18:39 ` tmoran [this message]
2004-05-23 21:04 ` Matthew Heaney
2004-05-24 7:13 ` Marius Amado Alves
2004-05-24 3:23 ` Matthew Heaney
2004-05-24 4:53 ` Simon Wright
2004-05-24 5:20 ` tmoran
2004-05-25 4:53 ` Simon Wright
2004-05-24 12:36 ` Matthew Heaney
2004-05-25 21:50 ` Robert I. Eachus
-- strict thread matches above, loose matches on Subject: below --
2004-05-22 21:18 Andrew Carroll
2004-05-22 21:46 ` tmoran
2004-05-23 11:21 ` Simon Wright
2004-05-24 18:26 ` tmoran
2004-05-25 5:10 ` Simon Wright
2004-05-25 6:37 ` tmoran
2004-05-23 9:43 ` Mark Lorenzen
2004-05-23 11:27 ` Simon Wright
2004-05-24 11:28 Andrew Carroll
2004-05-25 5:29 ` Simon Wright
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox