SergeychWorks/parsec3
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

license. opening it for public

Browse Source
This commit is contained in:
Sergey Chernov 2023-01-19 11:30:44 +01:00
parent c41d290b7d
commit 78c522b03a
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -4,10 +4,14 @@
Current stable version is __0.4.1-SNAPSHOT__. The full-dpulex RPC over websock is ok, the security level is still disabled until the protocol part will be sabilized. Current stable version is __0.4.1-SNAPSHOT__. The full-dpulex RPC over websock is ok, the security level is still disabled until the protocol part will be sabilized.
This is a connection-agnostic, full-duplex RPC type binary protocol, effective to work with binary data, such as encrypted data, keys, multimedia, etc. Its key points are: This is a connection-agnostic, kotlin multiplaftorm library providing full-duplex RPC type binary protocol, effective to work with binary data, such as encrypted data, keys, multimedia, etc. Default implementation uses websockets transport (binary frames) available on all supported platofrms (currently, JS and JVM).
Its key points are:
- simple and practical transport RPC layer, which is a primary choice when, for exaple, `wss://` level by TSL is enough, e.g. when there is no sensitive data being transmitted (games, etc). - simple and practical transport RPC layer, which is a primary choice when, for exaple, `wss://` level by TSL is enough, e.g. when there is no sensitive data being transmitted (games, etc).
- ktor server integration out of the box
- can easily be used with UDP (it has not too big binary frames that do not depend on the reception order) - can easily be used with UDP (it has not too big binary frames that do not depend on the reception order)
- asynchronous full-duplex multithreaded RPC: any number commands from both parties can be executed in parallel. - asynchronous full-duplex multithreaded RPC: any number commands from both parties can be executed in parallel.
@ -58,8 +62,8 @@ Not yet
Two reasons: Two reasons:
1. I don't want to depend on US crazy ideas like limit usage of its services to anybody who their governent won't like next week. 1. I don't want to depend on US crazy ideas like limit usage of its services to anybody who their governent won't like this week.
2. My ethic is against usage of open source in _paid services_ like gothub's copilot. 2. My ethic is against usage of open source in _paid services_ like GitHub's copilot.
### Why not universa? ### Why not universa?