On Mon, Dec 18, 2017 at 8:37 PM Yury Selivanov <yselivanov...@gmail.com> wrote:
> > 3. The connection pool has a queue, and creates a task for each > connection to serve requests from that queue. Naively, each task could > inherit the context of the request that caused it to be created, but the > task would outlive the request and go on to serve other requests. The > connection pool would need to specifically suppress the caller's context > when creating its worker tasks. > > I haven't used this pattern myself, but it looks like a good case for > adding a keyword-only 'context' rgument to `loop.create_task()`. This > way the pool can capture the context when some API method is called > and pass it down to the queue along with the request. The queue task > can then run connection code in that context. > > Yes, that would be useful. -Ben
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
