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

Author	asvetlov
Recipients	asvetlov, callumquick, malversan, yselivanov
Date	2019-11-04.15:07:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1572880078.89.0.994067665301.issue38285@roundup.psfhosted.org>
In-reply-to

Content
For each type, we need at least a test that creates a socket pair and successfully transfers data through the wire. I don't know what additional things are required. For example, on reading about SOCK_SEQ_PACKET I've found that recvmsg() is highly recommended over recv() to get messages boundaries. It obviously requires the new transport type and the new async protocol specification. Doesn't look trivial.

For each type, we need at least a test that creates a socket pair and successfully transfers data through the wire.

I don't know what additional things are required. For example, on reading about SOCK_SEQ_PACKET I've found that recvmsg() is highly recommended over recv() to get messages boundaries. It obviously requires the new transport type and the new async protocol specification.

Doesn't look trivial.

History
Date	User	Action	Args
2019-11-04 15:07:58	asvetlov	set	recipients: + asvetlov, yselivanov, malversan, callumquick
2019-11-04 15:07:58	asvetlov	set	messageid: <1572880078.89.0.994067665301.issue38285@roundup.psfhosted.org>
2019-11-04 15:07:58	asvetlov	link	issue38285 messages
2019-11-04 15:07:58	asvetlov	create