voidlizard
/
hbs2
mirror of https://github.com/voidlizard/hbs2
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,116 Commits 44 Branches 3 Tags 8.4 MiB
Commit Graph

26 Commits

Author SHA1 Message Date
voidlizard 6d69b40400 fix 2024-11-06 15:17:28 +03:00
voidlizard db15709e87 fix 2024-11-06 12:54:21 +03:00
voidlizard 5cb86b714d okay 2024-11-06 12:36:04 +03:00
voidlizard 73d9f7ec2c better 2024-11-06 11:47:56 +03:00
voidlizard ecf5add30d better? 2024-11-06 09:50:28 +03:00
voidlizard f11c17718f somehow works 2024-11-06 09:46:33 +03:00
voidlizard 9eaca26b45 fixed wtf 2024-11-05 19:45:34 +03:00
voidlizard 9b6496a89f fixed wtf 2024-11-05 19:25:59 +03:00
voidlizard bc160b8335 wip 2024-11-05 19:09:26 +03:00
voidlizard 405f749d61 wip 2024-11-05 14:11:30 +03:00
voidlizard 72659b7eb0 wip 2024-11-05 13:09:59 +03:00
voidlizard 572a5b4076 wip 2024-11-05 12:50:19 +03:00
voidlizard a91a25e647 fucked 2024-11-05 10:58:15 +03:00
voidlizard 71dd5d65b9 fucked 2024-11-05 09:19:25 +03:00
voidlizard cb5512d114 wip 2024-11-05 08:00:52 +03:00
voidlizard b9f7399b64 wip, block download rework 2024-11-04 13:40:07 +03:00
voidlizard 1aa2554d50 cache block sizes 2024-11-04 12:49:42 +03:00
voidlizard bb7ed502b4 wip 2024-11-04 12:11:50 +03:00
voidlizard 1baddb419c request-block-size 2024-11-04 08:04:21 +03:00
voidlizard 68baa0adb1 wip, tcp 2024-11-03 12:48:28 +03:00
voidlizard 25cf9a2040 wip 2024-11-03 12:10:02 +03:00
voidlizard acf89cd749 storage w. AnyProbe 2024-11-01 16:03:44 +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