WebSocket++
0.8.3-dev
C++ websocket client/server library
|
this feels hacky, is there a better way?
websocketpp Member websocketpp::versions_supported (helper, helper+4) Move this to configs to allow compile/runtime disabling or enabling of protocol versions
websocketpp::connection Member websocketpp::connection< config >::send (message_ptr msg) make exception system_error rather than error_code
websocketpp::connection Member websocketpp::connection< config >::write_frame () unit tests
websocketpp::connection Member websocketpp::connection< config >::handle_write_frame (lib::error_code const &ec) unit tests
this is not memory efficient. this value is not used after the handshake.
websocketpp::extensions::permessage_deflate::enabled Member websocketpp::extensions::permessage_deflate::enabled< config >::init (bool is_server) memory level, strategy, etc are hardcoded
websocketpp::extensions::permessage_deflate::enabled Member websocketpp::extensions::permessage_deflate::enabled< config >::enable_server_no_context_takeover () Document to what extent memory usage will be reduced
websocketpp::extensions::permessage_deflate::enabled Member websocketpp::extensions::permessage_deflate::enabled< config >::enable_client_no_context_takeover () Document to what extent memory usage will be reduced
websocketpp::extensions::permessage_deflate::enabled Member websocketpp::extensions::permessage_deflate::enabled< config >::compress (std::string const &in, std::string &out) : avail_in/out is 32 bit, need to fix for cases of >32 bit frames on 64 bit machines.
websocketpp::http::parser::parser Member websocketpp::http::parser::parser::set_version (std::string const &version) Does this method need any validation?
websocketpp::http::parser::parser Member websocketpp::http::parser::parser::append_header (std::string const &key, std::string const &val, lib::error_code &ec) Should there be any restrictions on which keys are allowed?
websocketpp::http::parser::parser Member websocketpp::http::parser::parser::process_header (std::string::iterator begin, std::string::iterator end) Update this method to be exception free.
websocketpp::processor::hybi00 Member websocketpp::processor::hybi00< config >::get_key3 () const This doesn't appear to be used anymore. It might be able to be removed
websocketpp::processor::hybi13 Member websocketpp::processor::hybi13< config >::validate_incoming_extended_header (frame::basic_header h, frame::extended_header e) const unit test for the >32 bit frames on 32 bit systems case
websocketpp::utility Member websocketpp::utility::ci_find_substr (T const &haystack, typename T::value_type const *needle, typename T::size_type size, std::locale const &loc=std::locale()) Is this still used? This method may not make sense.. should use iterators or be less generic. As is it is too tightly coupled to std::string