Paolo Pantellini (513a3a8d) at 22 Mar 13:07
Paolo Pantellini (def1bad7) at 22 Mar 13:07
Paolo Pantellini (51b01039) at 22 Mar 13:07
Paolo Pantellini (b03aa306) at 22 Mar 13:07
Paolo Pantellini (d0d8390c) at 22 Mar 13:06
Paolo Pantellini (e20696e4) at 22 Mar 13:06
Paolo Pantellini (fb500d7d) at 22 Mar 13:06
Paolo Pantellini (e20696e4) at 22 Mar 13:06
Paolo Pantellini (bc6f6066) at 22 Mar 12:51
We should materialize the gateway clients in the database, giving them persistence outside transfers. This would not only allow users to configure them, but it would also bring some new possibilities for configuring the gateway.
For example, by materializing the clients, we could restrict which network interface each of them is allowed to use. We could also restrict which partners each client is allowed to communicate with. This would indirectly allow users to restrict communication with some partners to a specific network interface. Materializing the clients would also indirectly allow users to restrict which protocols are allowed to be used by the gateway, since making a transfer would now require a client.
Paolo Pantellini (7e8278ec) at 22 Mar 12:51
Merge branch '332-materialize-the-gateway-clients' into 'master'
... and 4 more commits
Paolo Pantellini (bc6f6066) at 21 Mar 18:30
fix: Fixed clients sending server errors back to them & fixed the c...
... and 26 more commits
Bruno Carlin (9021d569) at 20 Mar 16:42
ci: use go 1.20 to build release binaries
Closes #64
Bruno Carlin (54e7bf6f) at 20 Mar 14:44
It breaks the compatibility with Windows 2003 server
Paolo Pantellini (3f0219c2) at 18 Mar 17:38
Those 2 methods will be needed to implement some of PESIT's functionality. The first one is needed to implement checkpoints, the second one is needed for restarts.