aquadoggo
aquadoggo copied to clipboard
p2panda
Node for the p2panda network handling validation, storage, aggregation and replication
Currently all services talk to all other services in `ServiceManager` and all worker pools get informed about all incoming tasks in `Factory`. This should not be a problem for now...
- a simple way to configure an aquadoggo - precursor to configuration via a configuration schema - should it be file based configuration?
Only start new replication session when we have new data for another node. The logic behind this is also needed for client subscriptions.
*Best reviewed commit by commit* The subscription field for receiving updates about a specific document is updated to trigger sending a new update whenever the materializer finishes a new version...
Prototype for GraphQL subscriptions that lets you stream the value of a single document, yields an update once a second. - Adds a WebSocket subscription endpoint - Adds a GraphQL...
Configuring a path like `~/Library/Application Data/aquadoggo/blobs` results in them being stored in that path relative to the working directory of aquadoggo instead of a path starting in the current user's...
I saw `orderBy` and `orderDirection` in the document. But it seems that it only support sorting by one field. So are there any chances to support multiple fields orderBy query?...
If the blob path is set but a directory doesn't exist at that location, then the node starts but later will crash if a blob is created. This results in...
https://github.com/p2panda/aquadoggo/blob/4809fab19382629237c109f4074b9b44312d0d12/aquadoggo/src/network/service.rs#L25 This timeout seems to be hit quite often, we can try and increase it. Also adding a delay between attempts would be nice.