➜

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 malversan
Recipients asvetlov, callumquick, malversan, yselivanov
Date 2019-11-04.16:41:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572885695.69.0.580657450759.issue38285@roundup.psfhosted.org>
In-reply-to
Content 
I do not have the answer about getting message boundaries at lower levels, but from a high-level point of view SOCK_SEQ_PACKET gives atomic reads, with no need to check for message boundaries yourself. Every time you read from a SOCK_SEQ_PACKET socket you get an entire message. That is the main difference with SOCK_STREAM, as far as I know.
History
Date User Action Args
2019-11-04 16:41:35malversansetrecipients: + malversan, asvetlov, yselivanov, callumquick
2019-11-04 16:41:35malversansetmessageid: <1572885695.69.0.580657450759.issue38285@roundup.psfhosted.org>
2019-11-04 16:41:35malversanlinkissue38285 messages
2019-11-04 16:41:35malversancreate