diff options
| author | YAMAMOTO Takashi <yamamoto@valinux.co.jp> | 2014-01-27 15:31:19 +0900 |
|---|---|---|
| committer | FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | 2014-01-27 22:22:09 +0900 |
| commit | bd235f1847d295b6d960981f03681db9d0dcc9c5 (patch) | |
| tree | 55f14a435c3eb2412310e97c189faf7dad796301 /doc/source | |
| parent | 3fcbaa15d0afe6d75864fa3356078a5c7fedb33f (diff) | |
doc: update after the sync request change
update documentation after commit c9325a22.
("fix bidirectional event confusion")
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Diffstat (limited to 'doc/source')
| -rw-r--r-- | doc/source/ryu_app_api.rst | 5 |
1 files changed, 1 insertions, 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. |