mirror of
https://github.com/Expand-sys/CCash
synced 2025-12-17 00:22:14 +11:00
📚🚧
This commit is contained in:
parent
d296e1da17
commit
a37825fd51
2 changed files with 18 additions and 2 deletions
|
|
@ -42,7 +42,6 @@ saving is done using FBE, this slightly reduces file size compared to JSON and i
|
||||||
| [Protobuf](https://developers.google.com/protocol-buffers) | 120 bytes | 628 ns | 759 ns |
|
| [Protobuf](https://developers.google.com/protocol-buffers) | 120 bytes | 628 ns | 759 ns |
|
||||||
| [JSON](http://rapidjson.org) | 301 bytes | 740 ns | 500 ns |
|
| [JSON](http://rapidjson.org) | 301 bytes | 740 ns | 500 ns |
|
||||||
## Multi-threading support
|
## Multi-threading support
|
||||||
considering phmap and drogon both massively benefit from being multi-threaded it seemed obvious that the entire program should be, this is enabled by default and manually settable at `MULTI_THREADED`. Below are some graphs visualizing the gain of doing so:
|
considering phmap and drogon both massively benefit from being multi-threaded it seemed obvious that the entire program should be, this is enabled by default and manually settable at `MULTI_THREADED`.
|
||||||
<!-- graph -->
|
|
||||||
## Backwards Compatible API
|
## Backwards Compatible API
|
||||||
versioning is implemented by the endpoints path, for example `/v1`. Breaking changes will ideally be sparse and backwards compatability will be maintained, for example ideally API `v3` instance can still run `v1` endpoints.
|
versioning is implemented by the endpoints path, for example `/v1`. Breaking changes will ideally be sparse and backwards compatability will be maintained, for example ideally API `v3` instance can still run `v1` endpoints.
|
||||||
|
|
|
||||||
|
|
@ -2,6 +2,23 @@
|
||||||
|
|
||||||
# Features
|
# Features
|
||||||
## Performance
|
## Performance
|
||||||
|
<!-- graphs -->
|
||||||
## Accessibility
|
## Accessibility
|
||||||
|
#### Connected Services
|
||||||
|
as explained in earlier docs a ecosystem of connected services allows you many ways to utilize CCash.
|
||||||
|
#### APIs
|
||||||
|
for devs who wanna make more connected services existing APIs exist in multiple lanaguages enabling faster development/maintenance.
|
||||||
|
#### External
|
||||||
|
its game indepedent meaning you dont have to be in-game to use it.
|
||||||
## Security
|
## Security
|
||||||
|
#### HTTPS
|
||||||
|
OpenSSL is used to secure the HTTP server.
|
||||||
|
#### Hashed Passwords
|
||||||
|
if the server's save file is compromised the user passwords will not be derivable.
|
||||||
## Other
|
## Other
|
||||||
|
#### Logs
|
||||||
|
each transaction is logged and the last `n` logs are stored, if set to 0 logs will be disabled.
|
||||||
|
#### Return On Delete
|
||||||
|
by default this feature is off, but when enabled deleted account's fund will be redirected to a specified account rather then "burned"
|
||||||
|
#### Configurable
|
||||||
|
as you can read in [building.md](../building.md) CCash is highly configurable.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue