Searched refs:start_next_cycle (Results 1 – 11 of 11) sorted by relevance
184 cs.start_next_cycle()190 cs.start_next_cycle()195 cs.start_next_cycle()207 cs.start_next_cycle()219 cs.start_next_cycle()230 cs.start_next_cycle()241 cs.start_next_cycle()
449 c.start_next_cycle()459 c.start_next_cycle()473 conn.start_next_cycle()516 c.start_next_cycle()530 c.start_next_cycle()620 conn.start_next_cycle()645 sc.start_next_cycle()809 c.start_next_cycle()
193 def start_next_cycle(self): member in Connection206 self._cstate.start_next_cycle()
298 def start_next_cycle(self): member in ConnectionState
403 .. automethod:: start_next_cycle422 This is preserved by :meth:`start_next_cycle`, so it can be472 * When calling :meth:`Connection.start_next_cycle`641 explicitly call :meth:`Connection.start_next_cycle` to reset both663 :meth:`~Connection.start_next_cycle`, and you can't call664 :meth:`~Connection.start_next_cycle` until the server has entered the673 completed and :meth:`~Connection.start_next_cycle` is called. See the742 :meth:`~Connection.start_next_cycle`.825 def start_next_cycle(self):826 self.conn.start_next_cycle()[all …]
87 * LocalProtocolError raised in start_next_cycle now shows states for204 :meth:`~Connection.start_next_cycle`.
314 client.conn.start_next_cycle()
221 self.conn.start_next_cycle()295 self.conn.start_next_cycle()
186 self._h11_state.start_next_cycle()
249 self.connection.start_next_cycle()