[erlang-questions] Using ssl (via ranch) {active, once} behaving like {active, twice}

[Loïc Hoguin]

Does it do it with normal SSL too or just with Ranch?

Depending on how you open the socket (for example using the {socket, 
Socket} option) it may have active set to once already, which means it 
will send the message beforehand. Ranch itself shouldn't, but if you 
open it manually it may happen.

On 09/08/2014 05:16 PM, Roger Lipscombe wrote:
> In R16B03-1, using SSL (with ranch) I'm seeing {active, once} behave
> as if it was {active, twice}.
>
> The client sends a message in 3 packets; I `receive` one packet, I
> call `recv`, which delivers the 3rd packet; process fails to parse the
> message and crashes; the crash log reveals that the 2nd packet is in
> the process message queue.
>
> What, if anything, am I doing wrong?
>
> Cheers,
> Roger.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>

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