libwebsockets/lib
Andy Green c511482c78 create server extension response dynamically
This goes through the extentsions the client requested, selects the ones
that we support at the server, and then further calls back to the appropriate
protocol callback in user code to check it's OK to actually use that
extension in this context.  If it is (callback unhandled == it is) then
it's added to the list of extensions sent back to the client.

Accepted extensions are also added to the connection's active extension
list and the private "user" memory allocation for the extension context is
done and bound to the connection.

Signed-off-by: Andy Green <andy@warmcat.com>
2011-03-06 10:29:35 +00:00
..
base64-decode.c introduce-client-support.patch 2011-01-22 12:51:57 +00:00
client-handshake.c introduce struct libwebsocket_extension 2011-03-05 16:12:15 +00:00
handshake.c create server extension response dynamically 2011-03-06 10:29:35 +00:00
libwebsockets.c create server extension response dynamically 2011-03-06 10:29:35 +00:00
libwebsockets.h create server extension response dynamically 2011-03-06 10:29:35 +00:00
Makefile.am uplevel-soname-and-spec-0.3.patch 2011-01-27 06:36:39 +00:00
Makefile.in uplevel-soname-and-spec-0.3.patch 2011-01-27 06:36:39 +00:00
md5.c introduce-private-md5-sha1.patch 2011-01-23 17:47:08 +00:00
parsers.c introduce win32 build capability 2011-03-02 22:03:47 +00:00
private-libwebsockets.h introduce struct libwebsocket_extension 2011-03-05 16:12:15 +00:00
sha-1.c introduce win32 build capability 2011-03-02 22:03:47 +00:00