96 | | === ```cgi::acceptor<>``` === |
97 | | Accepts connections. This should probably accept on only one connection type (meaning the ```gateway``` would be responsible for retrying an accept on a different connection type if that's allowed by the current protocol. |
98 | | |
99 | | === ```cgi::dispatcher<>``` === |
100 | | Completion handlers should be sent to a dispatcher to be called since a variety of dispatching methods should be available. The most basic/general is a thread-per-request dispatcher; more efficient would be a thread-pool dispatcher. Users should be able to implement their own dispatcher if they wish without having to know about any other class: encapsulation is important. ''Note: asio already has a dispatcher, so what can be used from that?'' |
| 96 | === ```cgi::basic_request_acceptor<>``` === |
| 97 | Accepts a new, possibly unloaded request. Before using the request `cgi::basic_request<>::load()` or `cgi::basic_request<>::async_load()` '''must''' be called. |