New submission from holger <holger...@freyther.de>: The current implementation verifies that the sock passed is a stream socket. This limitation appears to be arbitrary and is limiting.
* An AF_UNIX SOCK_DGRAM server socket becomes readable when one can accept(2) it. Just like SOCK_STREAM. * One could provide a different factory to create a reader/writer to use a SOCK_DGRAM socket (but most likely nothing special is needed) * A connected AF_UNIX SOCK_DGRAM socket will work with normal read/write messages just like SOCK_STREAM. AF_UNIX, SOCK_DGRAM is interesting because it provides a reliable transport for messages. This avoids having to write message segmentation or packing messages in any kind of envelope. ---------- components: asyncio messages: 311188 nosy: asvetlov, holger+lp, yselivanov priority: normal severity: normal status: open title: Make create_unix_server for SOCK_DGRAM work type: behavior versions: Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32715> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
