Commit Graph

30 Commits

Author SHA1 Message Date
voidlizard 899ec14feb much betta 2024-11-27 09:58:19 +03:00
voidlizard 048c8424fe code cleanup 2024-11-27 09:58:19 +03:00
voidlizard ad6871bca1 wip 2024-11-27 09:58:19 +03:00
voidlizard eabe88b94c wip 2024-11-27 09:58:19 +03:00
voidlizard 2c85db40e3 fix 2024-11-27 09:58:19 +03:00
voidlizard e0da057c36 fix 2024-11-27 09:58:19 +03:00
voidlizard a8e65de6e7 okay 2024-11-27 09:58:19 +03:00
voidlizard 77c8cd7d9f better 2024-11-27 09:58:19 +03:00
voidlizard 28fe6531c4 better? 2024-11-27 09:58:19 +03:00
voidlizard 3b7e94bc40 somehow works 2024-11-27 09:58:19 +03:00
voidlizard c4b919b85d fixed wtf 2024-11-27 09:58:19 +03:00
voidlizard ebf2014b98 fixed wtf 2024-11-27 09:58:19 +03:00
voidlizard 8435f16a15 wip 2024-11-27 09:58:19 +03:00
voidlizard 0bd62e50cc wip 2024-11-27 09:58:19 +03:00
voidlizard 783eed87f4 wip 2024-11-27 09:58:19 +03:00
voidlizard e5296cf894 wip 2024-11-27 09:58:19 +03:00
voidlizard b3628356cc fucked 2024-11-27 09:58:19 +03:00
voidlizard cfd02984f3 fucked 2024-11-27 09:58:19 +03:00
voidlizard 933a2e31ae wip 2024-11-27 09:58:19 +03:00
voidlizard ddd7485340 wip, block download rework 2024-11-27 09:58:19 +03:00
voidlizard 0adb3cc492 cache block sizes 2024-11-27 09:58:19 +03:00
voidlizard af40f12cae wip 2024-11-27 09:58:19 +03:00
voidlizard 40b38bc174 request-block-size 2024-11-27 09:58:19 +03:00
voidlizard 6862c81b27 wip, tcp 2024-11-27 09:58:18 +03:00
voidlizard 5bffbc1d03 wip 2024-11-27 09:58:18 +03:00
voidlizard 658bd53da5 storage w. AnyProbe 2024-11-27 09:57:59 +03:00
Dmitry Zuikov da6bb6bcb4 0.24.1 2024-03-20 08:17:22 +03:00
Dmitry Zuikov 850354c529 done expose-all-new-rpc 2023-10-06 05:48:17 +03:00
Dmitry Zuikov 28163d0123 storage rpc 2023-10-04 16:52:25 +03:00
Dmitry Zuikov 613f26e418 moved to RPC2
New RPC works over a Unix socket and assumes synchronous
requests with callService.

A new protocol, 'ServiceProto,' is introduced.

New RPC operates over a Unix socket.

Note the setting: (rpc2 unix "/tmp/hbs2-rpc2.socket").

The default rpc2 socket is located at /tmp/hbs2-rpc2.socket.

In the future, TCP RPC may be introduced, requiring only:

1. Authorization/Authentication

This might be accomplished through another wrapped protocol, for instance.

"Dialog"-associated elements are commented out for now,
as they will likely require their own Unix socket.
2023-10-04 10:54:39 +03:00