Can I implement asynchronous and non-blocking socket IO with boost.asio on LINUX?
Can I implement asynchronous and non-blocking (overlapped) socket IO with boost.asio on LINUX? If so please provide me some information for that. Thank you in advance! Best regards ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ----------------------------------------
On 04/14/2013 06:15 AM, Journeyer J. Joh wrote:
Can I implement asynchronous and non-blocking (overlapped) socket IO with boost.asio on LINUX? If so please provide me some information for that.
Yes, see the asynchronous examples in the tutorial: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/tutorial.html See also: http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/async...
Hi Bjorn Reese and poeple on list, Thank you for providing good url.
From the url below, http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/async...
I found a note below. Many operating systems offer a native asynchronous I/O API (such as overlapped I/O on *Windows*) as the preferred option for developing high performance network applications. The library may be implemented in terms of native asynchronous I/O. However, if native support is not available, the library may also be implemented using synchronous event demultiplexors that typify the Reactor pattern, such as*POSIX* select(). I think this implementation looks similar to ACE. The proactor implementation varies depends on platforms. ACE uses native asynch IO features for Windows, Solaris but not for LINUX. I wanted to know if boost.asio implements asynch IO for LINUX not like ACE. But the note above gives me an impression that boost.asio is almost the same with ACE for LINUX and other platforms also. Then does proactor of boost.asio on LINUX work well? If it is portable I guess it should though. Do people use proactor of boost.asio on LINUX? Sincerely Journeyer ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ---------------------------------------- 2013/4/14 Bjorn Reese <breese@mail1.stofanet.dk>
On 04/14/2013 06:15 AM, Journeyer J. Joh wrote:
Can I implement asynchronous and non-blocking (overlapped) socket IO with boost.asio on LINUX? If so please provide me some information for that.
Yes, see the asynchronous examples in the tutorial:
http://www.boost.org/doc/libs/**1_53_0/doc/html/boost_asio/** tutorial.html<http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/tutorial.html>
See also:
http://www.boost.org/doc/libs/**1_53_0/doc/html/boost_asio/** overview/core/async.html<http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/async.html>
______________________________**_________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/**mailman/listinfo.cgi/boost-**users<http://lists.boost.org/mailman/listinfo.cgi/boost-users>
From the url below, http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/async...
I found a note below.
Many operating systems offer a native asynchronous I/O API (such as overlapped I/O on Windows) as the preferred option for developing high performance network applications. The library may be implemented in terms of native asynchronous I/O. However, if native support is not available, the library may also be implemented using synchronous event demultiplexors that typify the Reactor pattern, such asPOSIX select().
I think this implementation looks similar to ACE. The proactor implementation varies depends on platforms. ACE uses native asynch IO features for Windows, Solaris but not for LINUX. I wanted to know if boost.asio implements asynch IO for LINUX not like ACE. But the note above gives me an impression that boost.asio is almost the same with ACE for LINUX and other platforms also.
The above note says that Asio relays on the native async. i/o where availble. Do you expect Asio to make use of native async. i/o where it's *unavailable*? The main difference between ACE and Asio is in their high-level interfaces.
participants (3)
-
Bjorn Reese -
Igor R -
Journeyer J. Joh