diff options
Diffstat (limited to 'examples/Reactor/Proactor/README')
| -rw-r--r-- | examples/Reactor/Proactor/README | 180 |
1 files changed, 0 insertions, 180 deletions
diff --git a/examples/Reactor/Proactor/README b/examples/Reactor/Proactor/README deleted file mode 100644 index 6509e3efcb4..00000000000 --- a/examples/Reactor/Proactor/README +++ /dev/null @@ -1,180 +0,0 @@ -This README file lists all the example applications for the Proactor framework. - -Test/Example Applications for Proactor: -========================================= - -The following tests are available. - -o $ACE_ROOT/tests/Aio_Platform_Test.cpp : Tests basic limits - pertaining to the POSIX features - -o $ACE_ROOT/examples/Reactor/Proactor/test_aiocb.cpp : - This is a C++ program for testing the AIOCB (AIO Control - Blocks) based completion approach which uses <aio_suspend> for - completion querying. - -o $ACE_ROOT/examples/Reactor/Proactor/test_aiosig.cpp : This is a - C++ program for testing the Signal based completion approach - that uses <sigtimedwait> for completion querying. - -o $ACE_ROOT/examples/Reactor/Proactor/test_aiocb_ace.cpp: Portable - version of test_aiocb.cpp. (Same as test_aiocb.cpp, but uses - ACE_DEBUGs instead of printf's and ACE_Message_Blocks instead - of char*'s. - -o $ACE_ROOT/examples/Reactor/Proactor/test_aiosig_ace.cpp: Portable - version of test_aiosig.cpp. (Same as test_aiosig.cpp, but uses - ACE_DEBUGs instead of printf's and ACE_Message_Blocks instead - of char*'s. - -o test_proactor.cpp (with ACE_POSIX_AIOCB_Proactor) : Test for - ACE_Proactor which uses AIOCB (AIO Control Blocks) based - completions strategy Proactor. (#define - ACE_POSIX_AIOCB_PROACTOR in the config file, but this is the - default option) - -o test_proactor.cpp (with ACE_POSIX_SIG_Proactor) : Test for - ACE_Proactor which uses real time signal based completion - strategy proactor. (#define ACE_POSIX_SIG_PROACTOR in the - config file) - -o test_multiple_loops.cpp : This example application shows how - to write programs that combine the Proactor and Reactor event - loops. This is possible only on WIN32 platform. - -o test_timeout.cpp : Multithreaded application testing the Timers - mechanism of the Proactor. - -o test_timeout_st.cpp : Sinle threaded version of test_timeout.cpp. - - - -Behavior of POSIX AIO of various platforms: -========================================== - - - -Summary: -====== - Sun Sun Lynx - 5.6 5.7 - -test_aiocb_ace Good Good Good -(test_aiocb) - -test_aiosig_ace Inconst Inconst Inconst - - -Inconst.: Inconsistent execution. - - - -Aio_Platform_Test: -================ - - -Sun5.6 CC: ---------- - Status : OK - - Problems: 1.The constant which indicates the maximum - concurrent asynchronous I/Os is -1 at run - time. This should be atleast 1. - -Sun57 CC: --------- - Status : OK - - Problems: <Same as in sun56 CC> - -Lynx g++: --------- - Status : OK - - Problems: AIO_LISTIO_MAX, AIO_MAX and SIGQUEUE_MAX are defined - but their values are -1 - -test_aiocb.cpp -============= - -Sun5.6 CC: ---------- - Status : GOOD - - Problems: NONE - -Sun57 CC: --------- - Status : GOOD - - Problems: NONE - -Lynx g++: --------- - - - -test_aiosig.cpp: -=============== - -Sun5.6 CC: ---------- - Status : GOOD - - Problems: NONE - -Sun57 CC: --------- - Status : BAD - - Problems: 1. If 2 <aio_> calls are issed, only one completion - gets through, second one hangs. - -Lynx g++: --------- - - - -test_aiosig_ace.cpp: -==================== - -Sun5.6 CC: ---------- - Status : BAD - - Problems: 1. <aio_read> and <aio_write> calls return 0 but - sets the<errno> to 48 which is <Operation Not - Supported> - - 2. I issue <aio_read/write> with a RT signal enabled. It - returns but with the a wrong signal code, -2, which is - SI_QUEUE. But we are supposed to get SI_ASYNCIO - - 3*.IMPORTANT: If I issue two <aio_read/write> calls, - they get queued and - they execute correctly. But their completions are not - queued up correctly. - - 4. Calling <sigtimedwait> sometimes print the string - "err = 22". But <sigtimedwait> doesnt return a error and - errno is also not set to any error values. (err == 22, may - be referring to errno 22 which means Invalid Argument) - -Sun57 CC: --------- - Status : BAD - - Problems: <same as in sun56 CC> - -Lynx g++: --------- - - Status : OK - - Problems: 1. In between my Proactor test application the - <errno> is getting set to <77>. This means - Unsupported POSIX operation. But none of my - <posix> calls return -1. - - TO-DO : 1. Run <gdb> and watch for <errno> and figure when - it is changing over to 77. |