Mukund Sivaraman
713e348235
[master] Use libtool from top_builddir
|
il y a 13 ans | |
|---|---|---|
| .. | ||
| doc | il y a 14 ans | |
| tests | il y a 13 ans | |
| Makefile.am | il y a 13 ans | |
| README | il y a 14 ans | |
| asiolink.h | il y a 14 ans | |
| dummy_io_cb.h | il y a 14 ans | |
| interval_timer.cc | il y a 14 ans | |
| interval_timer.h | il y a 14 ans | |
| io_address.cc | il y a 13 ans | |
| io_address.h | il y a 13 ans | |
| io_asio_socket.h | il y a 13 ans | |
| io_endpoint.cc | il y a 13 ans | |
| io_endpoint.h | il y a 13 ans | |
| io_error.h | il y a 14 ans | |
| io_message.h | il y a 14 ans | |
| io_service.cc | il y a 13 ans | |
| io_service.h | il y a 14 ans | |
| io_socket.cc | il y a 14 ans | |
| io_socket.h | il y a 14 ans | |
| simple_callback.h | il y a 13 ans | |
| tcp_endpoint.h | il y a 14 ans | |
| tcp_socket.h | il y a 13 ans | |
| udp_endpoint.h | il y a 14 ans | |
| udp_socket.h | il y a 14 ans | |
README
The asiolink library is intended to provide an abstraction layer between
BIND10 modules and the socket I/O subsystem we are using (currently, the
headers-only version of ASIO, release 1.43). This has several benefits,
including:
- Simple interface
- Back-end flexibility: It would be easy to switch from using
ASIO to boost::asio, and even relatively straightforward to switch
to any other asynchronous I/O system.
- Cleaner compilation: The ASIO headers include code which can
generate warnings in some compilers due to unused parameters and
such. Including ASIO header files throughout the BIND 10 tree would
require us to relax the strictness of our error checking. Including
them in only one place allows us to relax strictness here, while
leaving it in place elsewhere.
Some of the classes defined here--for example, IOSocket, IOEndpoint,
and IOAddress--are to be used by BIND 10 modules as wrappers around
ASIO-specific classes.
Logging
-------
At this point, nothing is logged by this low-level library. We may
revisit that in the future, if we find suitable messages to log, but
right now there are also no loggers initialized or called.
BIND10 modules and the socket I/O subsystem we are using (currently, the
headers-only version of ASIO, release 1.43). This has several benefits,
including:
- Simple interface
- Back-end flexibility: It would be easy to switch from using
ASIO to boost::asio, and even relatively straightforward to switch
to any other asynchronous I/O system.
- Cleaner compilation: The ASIO headers include code which can
generate warnings in some compilers due to unused parameters and
such. Including ASIO header files throughout the BIND 10 tree would
require us to relax the strictness of our error checking. Including
them in only one place allows us to relax strictness here, while
leaving it in place elsewhere.
Some of the classes defined here--for example, IOSocket, IOEndpoint,
and IOAddress--are to be used by BIND 10 modules as wrappers around
ASIO-specific classes.
Logging
-------
At this point, nothing is logged by this low-level library. We may
revisit that in the future, if we find suitable messages to log, but
right now there are also no loggers initialized or called.