Member websocketpp::connection< config >::buffered_amount () const: use get_buffered_amount instead
Member websocketpp::http::parser::response::consume (std::istream &s, lib::error_code &ec): 0.9.0 This overload is dangerous in that it can overread the stream and there isn't a good way to recover bytes lost this way. As of 0.9.0 an error is raised when this situation happens, but generally, it would be better for the calling application to read the stream itself and call consume(char const *, size_t, lib::error_code) instead which provides a better method of identifying and recovering from overreads.
Member websocketpp::server< config >::get_connection (): 0.9.0 use get_connection(lib::error_code &) instead.
Member websocketpp::server< config >::loop (exception) void start_accept(): use start_accept(accept_loop_handler) instead
Member websocketpp::server< config >::start_accept (accept_loop_handler completion_handler): use `start_accept(accept_loop_handler) instead
Member websocketpp::transport::asio::connection< config >::set_tcp_init_handler (tcp_init_handler h): Use set_tcp_pre_init_handler instead
Member websocketpp::transport::asio::endpoint< config >::set_tcp_init_handler (tcp_init_handler h): Use set_tcp_pre_init_handler instead
Member websocketpp::transport::iostream::connection< config >::readsome (char const *buf, size_t len): DEPRECATED in favor of read_some()