That will be perfect ‘if’ you prepend the 4 integer bytes of the size of the content to your json data. 
I found this to help: http://stackoverflow.com/questions/9742449/sending-sockets-data-with-a-leading-length-value
Do note it must be in network-byte order, so if the length seems wrong (as in you may not receive anything) swap the bytes, it must be in network-byte order.
But according to the link, you’ll use the php pack function/2 (probably the ‘N’ option I think).
i have response like this
<<0, 0, 26, 53, 123, 34, 97, 99, 116, 105, 111, 110, 34, 58, 34, 68, 101, 99,
105, 115, 105, 111, 110, 67, 111, 109, 112, 108, 101, 116, 101, 100, 34, 44,
34, 117, 117, 105, 100, 34, 58, 34, 56, 54, 52, 98, 54, 99, 102, 99, …>>
received: "b3815b922fee5f88ced775c28","position":"+0|0+8|0","action":"ScheduleTask","input":"{\"data\":{\"n\":\"{\\\"data\\\":4}\"}}"},{"name":"EchoDuration","hash":"83e93c3b3815b922fee5f88ced775c28","position":"+0|0+9|0","action":"ScheduleTask","input":"{\"data\":{\"n\":\"{\\\"data\\\":4}\"}}"},{"name":"EchoDuration","hash":"83e93c3b3815b922fee5f88ced775c28\
I’ve done everything you tell me and i have response like this, I don’t really understand how can i manage it after ? Sorry but i’m not used to socket protocol
Can you show your code? That is not looking like {:packet, 4} is set? Though the data looks good now.
defmodule TaskyRabbit.Socket do
use GenServer
defmodule State do
defstruct port: nil, lsock: nil, socket: nil
end
#######
# API #
#######
def start_link(port) do
GenServer.start_link(__MODULE__, port, name: __MODULE__)
end
def init(port) do
IO.puts(port)
current = self()
# tcp_options = [:binaries, {:packet, 0}, {:active, false}, {:reuseaddr, true}]
# tcp_options = [:binary, packet: 0, active: false, reuseaddr: true]
{:ok, l_socket} = :gen_tcp.listen(port, [:binary, {:packet, 4}, {:packet, :line}, active: false, reuseaddr: true])
send(current, :accept)
{:ok, %State{port: port, socket: l_socket}}
end
def handle_info(:accept, state = %{socket: socket}) do
do_listen(socket)
{:noreply, state}
end
defp do_listen(l_socket) do
{:ok, socket} = :gen_tcp.accept(l_socket)
spawn(fn() -> do_server(socket) end)
do_listen(l_socket)
end
defp do_server(socket, string \\ "") do
case :gen_tcp.recv(socket, 0) do
{ :ok, data } ->
case message = Poison.Parser.parse(data) do
{:ok, json} ->
IO.puts "good"
{:error, :invalid, t} ->
new_string = "#{string}#{data}"
do_server(socket, data)
{:error, {:invalid, t, _}} ->
do_server(socket, data)
end
IO.inspect (data), label: "received"
# TaskyRabbit.tcp_rbmq(data)
{ :error, :closed } ->
IO.inspect "closed"
:ok
end
end
end
$host = "127.0.0.1";
$port = 4040;
$json = json_encode($response);
$length=pack("N",strlen($json));
$socket = socket_create(AF_INET6, SOCK_STREAM, SOL_TCP);
$connection = socket_connect($socket, $host, $port);
socket_write($socket, $length.$json, 4+strlen($json));
Duplicates detected! ^.^ Remove the , {:packet, :line} part, that is overriding the {:packet, 4} option.
Correct, that is only if you are doing a line-oriented protocol. By putting a prefix-length you are doing a length-oriented protocol (which is always superior in my opinion as you can represent *anything* in it).
Only one or the other.
Heh, I’ve written a LOT of TCP and UDP (and SCTP) protocols over the past 25 years, many in erlang itself, so I like to help when I can. ^.^