Re: [Flightgear-devel] Set websocket update rate.

[www2 <ww...@wo...>]

James

I feel that i am one of the ask this for a long time.

what  current understand is that with the generic protocol is that the
command:
fgfs --generic=socket,in,5,127.0.0.3,1234,tcp,abc-protocol
act as a server that reseve data and the command
fgfs --generic=socket,out,5,127.0.0.3,1234,tcp,abc-protocol
act as a client that send only send.
(disclaimer i need to test this for id this is correct or this is revert
what i say)
some thing like a option tcpS/udpS (S for server) and tcpC/udpC (C for
client) with the code change can be a option to fix this problem.

Jean-Paul Anceaux (www2)

Op 12-06-2023 om 11:20 schreef James Turner:
> 
> 
>> On 12 Jun 2023, at 10:14, www2 <ww...@wo...> wrote:
>>
>> An other issue that i see that will be fix in the network code (TCP) is
>> that is no bi direction communication possible with custom protocols
>> ($FGROOT/Protocol/*.xml)
> 
> This is one of those weird questions / issues that comes up every year
> (more o rless) : there definitely is some place in the code that
> historically did not support bidirectional protocols, but now does. 
> 
> TCP is of course bidirectional, and in the encode/decode pieces, there
> is absolutely no reason we cannot support both directions.
> 
> So I wonder, why this ‘no bidrectional’ thing still hangs around: do we
> still miss some technical piece? Or just have some out of date documents
> or no good example of how it actually use it bidirectionally?
> 
> Unfortunately it’s not an area I can invest a lot of time, but I feel a
> small amount of looking into the code would fix this for everyone.
> 
> Kind regards,
> James
> 
> 
> 
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel