Remove pause/resume_writing() and discard_output(). Mention asyncio name. Clarify callback serialization.

pep-3156.txt

@@ -1,5 +1,5 @@
 PEP: 3156
-Title: Asynchronous IO Support Rebooted
+Title: Asynchronous IO Support Rebooted: the "asyncio" Module
 Version: $Revision$
 Last-Modified: $Date$
 Author: Guido van Rossum <guido@python.org>
@@ -21,6 +21,9 @@ higher-level scheduler based on ``yield from`` (PEP 380).  A reference
 implementation is in the works under the code name Tulip.  The Tulip
 repo is linked from the References section at the end.
 
+The proposed standard library module name is ``asyncio``, although the
+rest of this PEP has not yet been updated to reflect this.
+
 
 Introduction
 ============
@@ -363,7 +366,9 @@ Basic Callbacks
   called as soon as possible.  Returns a Handle representing the
   callback, whose ``cancel()`` method can be used to cancel the
   callback.  It guarantees that callbacks are called in the order in
-  which they were scheduled.
+  which they were scheduled.  Callbacks associated with the same event
+  loop are strictly serialized -- one callback must exit before the
+  next one will be called.
 
 - ``call_later(delay, callback, *args)``.  Arrange for
   ``callback(*args)`` to be called approximately ``delay`` seconds in
@@ -1024,16 +1029,6 @@ Bidirectional stream transports have the following public methods:
 - ``resume()``.  Restart delivery of data to the protocol via
   ``data_received()``.
 
-- ``pause_writing()``.  Suspend sending data to the network until a
-  subsequent ``resume_writing()`` call.  Between ``pause_writing()``
-  and ``resume_writing()`` the transport's ``write()`` method will
-  just be accumulating data in an internal buffer.
-
-- ``resume_writing()``.  Restart sending data to the network.
-
-- ``discard_output()``.  Discard all data buffered by ``write()`` but
-  not yet sent to the network.
-
 - ``close()``.  Sever the connection with the entity at the other end.
   Any data buffered by ``write()`` will (eventually) be transferred
   before the connection is actually closed.  The protocol's