From bd235f1847d295b6d960981f03681db9d0dcc9c5 Mon Sep 17 00:00:00 2001 From: YAMAMOTO Takashi Date: Mon, 27 Jan 2014 15:31:19 +0900 Subject: doc: update after the sync request change update documentation after commit c9325a22. ("fix bidirectional event confusion") Signed-off-by: YAMAMOTO Takashi Signed-off-by: FUJITA Tomonori --- 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 5c0b5365..7306c2e5 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. -- cgit v1.2.3