JINMEI Tatuya
e4034daa01
[trac812] reduce dependency: removed unused function in lib/dns/tests/
|
14 years ago | |
|---|---|---|
| .. | ||
| doc | 14 years ago | |
| tests | 14 years ago | |
| Makefile.am | 14 years ago | |
| README | 14 years ago | |
| asiolink.h | 14 years ago | |
| dummy_io_cb.h | 14 years ago | |
| interval_timer.cc | 14 years ago | |
| interval_timer.h | 14 years ago | |
| io_address.cc | 14 years ago | |
| io_address.h | 14 years ago | |
| io_asio_socket.h | 14 years ago | |
| io_endpoint.cc | 14 years ago | |
| io_endpoint.h | 14 years ago | |
| io_error.h | 14 years ago | |
| io_message.h | 14 years ago | |
| io_service.cc | 14 years ago | |
| io_service.h | 14 years ago | |
| io_socket.cc | 14 years ago | |
| io_socket.h | 14 years ago | |
| simple_callback.h | 14 years ago | |
| tcp_endpoint.h | 14 years ago | |
| tcp_socket.h | 14 years ago | |
| udp_endpoint.h | 14 years ago | |
| udp_socket.h | 14 years ago | |
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.
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.