|
From: James T. <ja...@fl...> - 2023-06-12 09:20:40
|
> 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 |