iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Augment section on datagrams a little.

This commit is contained in:
Guido van Rossum 2013-01-04 15:58:48 -08:00
parent facc0c00cc
commit c8d7d9afd0
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-3156.txt
View File

@ -884,11 +884,15 @@ Open Issues
(because to wait for a lock we'd have to use ``yield from``, which
the ``with`` statement can't do).
- Support for datagram protocols, "connected" or otherwise? Probably
- Support for datagram protocols, "connected" or otherwise. Probably
need more socket I/O methods, e.g. ``sock_sendto()`` and
``sock_recvfrom()``. Or users can write their own (it's not rocket
science). Is it reasonable to map ``write()``, ``writelines()``,
``data_received()`` to single datagrams?
``data_received()`` to single datagrams? Or should we have a
different ``datagram_received()`` method on datagram protocols?
(Glyph recommends the latter.) And then what instead of ``write()``?
Finally, do we need support for unconnected datagram protocols?
(That would mean wrappers for ``sendto()`` and ``recvfrom()``.)
- An EventEmitter in the style of NodeJS? Or make this a separate
PEP? It's easy enough to do in user space, though it may benefit