From 37934f8b5abbd651b327e2186b489a747596cb26 Mon Sep 17 00:00:00 2001 From: David Wilson Date: Thu, 24 Aug 2017 17:25:55 +0530 Subject: [PATCH] Document GET_MODULE in a slave context. --- docs/howitworks.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/howitworks.rst b/docs/howitworks.rst index 4875c17d..d11bc402 100644 --- a/docs/howitworks.rst +++ b/docs/howitworks.rst @@ -273,6 +273,7 @@ Masters listen on the following handles: module named ``fullname``, and writes the source along with some metadata back to the handle ``reply_to``. If lookup fails, ``None`` is sent instead. + Slaves listen on the following handles: .. data:: econtext.core.CALL_FUNCTION @@ -306,6 +307,20 @@ Slaves listen on the following handles: establishment. +Slaves that have ever been used to create a descendent child context also +listen on the following handles: + +.. data:: econtext.core.GET_MODULE + + As with master's ``GET_MODULE``, except this implementation + (`:py:class:econtext.master.ModuleForwarder`) serves responses using + :py:class:`econtext.core.Importer`'s cache before forwarding the request to + its parent context. The response is cached by each context in turn before + being forwarded on to the slave context that originally made the request. + In this way, the master need never re-send a module it has already sent to + a direct descendant. + + Additional handles are created to receive the result of every function call triggered by :py:meth:`call_with_deadline() `.