Message 180328 - 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	neologix
Recipients	giampaolo.rodola, gvanrossum, jcea, neologix, pitrou, sbt, trent
Date	2013年01月20日.22:45:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1358721957.27.0.919987384037.issue16507@psf.upfronthosting.co.za>

Content
Time for a stupid question from someone who doesn't know anything about Windows: if WSAPoll() is really terminally broken, is it really worth the hassle exposing it and warping the API? AFAICT, FD_SETSIZE is already bumped to 512 on Windows, and Windows select() is limited by the fd_set size, not the maximum descriptor: so what exactly does WSAPoll() bring over select() on Windows? (Especially if there are plans to support IOCP, wouldn't that make WSAPoll() obsolete?)

Content

Time for a stupid question from someone who doesn't know anything about Windows: if WSAPoll() is really terminally broken, is it really worth the hassle exposing it and warping the API?
AFAICT, FD_SETSIZE is already bumped to 512 on Windows, and Windows select() is limited by the fd_set size, not the maximum descriptor: so what exactly does WSAPoll() bring over select() on Windows?
(Especially if there are plans to support IOCP, wouldn't that make WSAPoll() obsolete?)

History
Date	User	Action	Args
2013年01月20日 22:45:57	neologix	set	recipients: + neologix, gvanrossum, jcea, pitrou, giampaolo.rodola, trent, sbt
2013年01月20日 22:45:57	neologix	set	messageid: <1358721957.27.0.919987384037.issue16507@psf.upfronthosting.co.za>
2013年01月20日 22:45:57	neologix	link	issue16507 messages
2013年01月20日 22:45:56	neologix	create

homepage