diff options
| author | Andy Green <andy@warmcat.com> | 2011-03-06 13:15:29 +0000 |
|---|---|---|
| committer | Andy Green <andy@warmcat.com> | 2011-03-06 13:15:29 +0000 |
| commit | c6517fa2ad3ffa69a04194f971b6cab414f0a243 (patch) | |
| tree | dd8be8a66a741f7464b33df68b3761ba55ce0f6d /libwebsockets-api-doc.html | |
| parent | 57b4e9af2bc7fc2874d52c9b8a8c2cf9b5168560 (diff) | |
dynamically create client extensions offer from extensions list
Signed-off-by: Andy Green <andy@warmcat.com>
Diffstat (limited to 'libwebsockets-api-doc.html')
| -rw-r--r-- | libwebsockets-api-doc.html | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/libwebsockets-api-doc.html b/libwebsockets-api-doc.html index 4693387..a82383b 100644 --- a/libwebsockets-api-doc.html +++ b/libwebsockets-api-doc.html @@ -664,6 +664,17 @@ valid. Note though at this time the ESTABLISHED callback hasn't happened yet so if you initialize <tt><b>user</b></tt> content there, <tt><b>user</b></tt> content during this callback might not be useful for anything. Notice this callback comes to protocols[0]. +</blockquote> +<h3>LWS_CALLBACK_CLIENT_CONFIRM_EXTENSION_SUPPORTED</h3> +<blockquote> +When a client +connection is being prepared to start a handshake to a server, +each supported extension is checked with protocols[0] callback +with this reason, giving the user code a chance to suppress the +claim to support that extension by returning non-zero. If +unhandled, by default 0 will be returned and the extension +support included in the header to the server. Notice this +callback comes to protocols[0]. <p> The next four reasons are optional and only need taking care of if you will be integrating libwebsockets sockets into an external polling |