update documentation after commit c9325a22.
("fix bidirectional event confusion")

Signed-off-by: YAMAMOTO Takashi <[email protected]>
---
 doc/source/ryu_app_api.rst | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/source/ryu_app_api.rst b/doc/source/ryu_app_api.rst
index 5c0b536..7306c2e 100644
--- a/doc/source/ryu_app_api.rst
+++ b/doc/source/ryu_app_api.rst
@@ -32,11 +32,8 @@ the Ryu application will be processed.
 There are kinds of events which are used to implement synchronous
 inter-application calls between Ryu applications.
 While such requests uses the same machinary as ordinary
-events, their replies are put on another queue dedicated to replies
+events, their replies are put on a queue dedicated to the transaction
 to avoid deadlock.
-(Because, unlike erlang, our queue doesn't support selective receive.)
-It's assumed that the number of in-flight synchronous requests from
-a Ryu application is at most 1.
 
 While threads and queues is currently implemented with eventlet/greenlet,
 a direct use of them in a Ryu application is strongly discouraged.
-- 
1.8.3.1


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to