[Libwebsockets] question on websockets protocol name - required?
"Andy Green (林安廸)"
andy at warmcat.com
Sat Jan 11 05:52:42 CET 2014
On 08/01/14 06:08, the mail apparently from Michael Haberler included:
> to answer my own question:
> Am 06.01.2014 um 22:19 schrieb Michael Haberler
> <andy.green at linaro.org>:
>> so far - looking at examples and being a websocket noob - I was
>> under the impression one had to have a protocols struct with a
>> websocket protocol name, requiring the client to send a
>> "Sec-WebSocket-Protocol: <protocolname>" header
>> now I found this, which just gets away with a single http-only
>> protocol entry:
>>this would make it simpler for some clients which dont support a
protocol name out of the box, like
>> question - assume I used this:
>> can I still serve http and websockets from a single callback?
> yes - sessions without a Sec-WebSocket-Protocol: header will be
> funneled through the protocol 0 handler (http)
Right... the callbacks for the various actions are all mutually
exclusive, so for example one callback can handle both the client and
server sides of a protocol.
The only thing special about protocol is HTTP and extpoll stuff
specifically targets protocol, it doesn't stop you using it as a real
protocol. But for the test code, it's easier to understand what's
happening to separate the callbacks.
> using a protocol name on the client side will abort the session ('Req
> protocol <protocolname> not supported')
>> or would that force the scheme to serve only websockets?
Right the HTTP serving thing can support anything from HTTP, it's not
restricted to only websocket upgrade activities.
>> thanks in advance,
>> *) it still does, just needs header=["Sec-WebSocket-Protocol:
>> <protocolname>"] in the websocket.WebSocketApp() instantiation
>> _______________________________________________ Libwebsockets
>> mailing list Libwebsockets at ml.libwebsockets.org
> _______________________________________________ Libwebsockets mailing
> list Libwebsockets at ml.libwebsockets.org
More information about the Libwebsockets