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

19 Commits

Author SHA1 Message Date
voidlizard 658bd53da5 storage w. AnyProbe 2024-11-27 09:57:59 +03:00
voidlizard 3fb0be2692 fixed-messaging-and-basic-probes 2024-11-27 09:57:42 +03:00
voidlizard e98207f5b9 fixed-messaging-and-basic-probes 2024-11-27 09:57:42 +03:00
Yura Shelyag ed7a402fc3 Fixed die and SIGINT exit 2024-11-01 16:02:08 +03:00
Dmitry Zuikov 9bab121743 merged hbs2-cli ans hbs2-sync 2024-08-07 15:20:19 +03:00
Dmitry Zuikov da6bb6bcb4 0.24.1 2024-03-20 08:17:22 +03:00
Dmitry Zuikov e9c7c9dbae merged new download and some intermediate changes 2024-03-06 16:10:24 +03:00
Dmitry Zuikov cc7f2dd948 download fixes 2024-02-21 05:55:13 +03:00
Dmitry Zuikov c44a6b997b new protocol encryption + minor tuning 2023-10-25 09:01:23 +03:00
Dmitry Zuikov 98e589fe6f fixed-block-download-control 2023-10-20 11:16:11 +03:00
Dmitry Zuikov 29fdd23602 fixed reflog sync bug 2023-10-18 10:16:11 +03:00
Dmitry Zuikov d3c63ab8e4 accept reflogupdate only for subcribed refs or from friendly peers 2023-10-15 09:26:49 +03:00
Dmitry Zuikov 64400a425e dynamic polling management 2023-10-13 10:06:17 +03:00
Dmitry Zuikov 155765038e removed obsolete file 2023-10-09 03:29:01 +03:00
Dmitry Zuikov 8842843ffb hbs2-git-to-new-rpc 2023-10-07 14:29:40 +03:00
Dmitry Zuikov 850354c529 done expose-all-new-rpc 2023-10-06 05:48:17 +03:00
Dmitry Zuikov 15d6a1d06f modular-rpc-api 
1. Making the API modular
2. Running all via single socket, including storage
 2023-10-05 11:54:36 +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