[99s-extend] cowboy_websocket_handler

Loïc Hoguin essen at ninenines.eu
Thu Apr 23 10:55:23 CEST 2015


It's a simple function call.

Assuming the variable Handler contains the name of the module, it's just 
doing Handler:websocket_info(Info, Req, State) and then checks the 
return value.

On 04/23/2015 12:39 AM, Samir Sow wrote:
> Thanks.
> Still i can’t figure out how you manage the data transmission from/to handler via the websocket_handle() and websocket_info() function.
>
> Samir
>
>> On 22 avr. 2015, at 23:18, Loïc Hoguin <essen at ninenines.eu> wrote:
>>
>> Hello,
>>
>> On 04/22/2015 11:56 PM, Samir Sow wrote:
>>> I would like to learn more about the cowboy_xxxx_handler for instance the cowboy_websocket_handler  :
>>> -  is it an OTP gen_ instance ?
>>> - how/where the websocket_handle() is called ?
>>> - how websocket_info() relates to the Transport:send() operation and where/how this latter function is called?
>>>
>>> I  could not find the cowboy_websocket_handler behavior in the src dir. I guess i’ve missed something.
>>> The code is clean but difficult to decipher by a erlang padawan like me.
>>
>> Presumably you are looking in master. cowboy_websocket does that in master now. cowboy_websocket_handler is in Cowboy 1.0.
>>
>> --
>> Loïc Hoguin
>> http://ninenines.eu
>

-- 
Loïc Hoguin
http://ninenines.eu


More information about the Extend mailing list