Message 156354 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	sbt
Recipients	giampaolo.rodola, kristjan.jonsson, sbt
Date	2012年03月19日.19:01:20
SpamBayes Score	8.6973095e-11
Marked as misclassified	No
Message-id	<1332183681.49.0.656385290208.issue14310@psf.upfronthosting.co.za>

Content
> I think this captures the functionality better than "duplicate" or > duppid() since there is no actual duplication involved until the > fromshare() function is called. Are you saying the WSADuplicateSocket() call in share() doesn't duplicate the handle in to the target process? I am pretty sure it does. (Delaying handle duplication till WSASocket() is called in the target process would be rather problematic since then you cannot close the original socket in the source processes until you know the duplication has occurred.)

Content

> I think this captures the functionality better than "duplicate" or 
> duppid() since there is no actual duplication involved until the 
> fromshare() function is called.
Are you saying the WSADuplicateSocket() call in share() doesn't duplicate the handle in to the target process? I am pretty sure it does.
(Delaying handle duplication till WSASocket() is called in the target process would be rather problematic since then you cannot close the original socket in the source processes until you know the duplication has occurred.)

History
Date	User	Action	Args
2012年03月19日 19:01:21	sbt	set	recipients: + sbt, kristjan.jonsson, giampaolo.rodola
2012年03月19日 19:01:21	sbt	set	messageid: <1332183681.49.0.656385290208.issue14310@psf.upfronthosting.co.za>
2012年03月19日 19:01:20	sbt	link	issue14310 messages
2012年03月19日 19:01:20	sbt	create

homepage