Kaladaran/briar
0
0
Fork 0
mirror of https://code.briarproject.org/briar/briar.git synced 2026-02-20 06:39:54 +01:00
Code Issues Projects Releases Wiki Activity

s/channel/group/g

akwizgran
2016-01-20 17:06:19 +00:00
parent 3164b94437
commit 06d4da102d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ClientApiNotes.md

@@ -19,11 +19,11 @@ Use cases to consider:
Considering the above issues and uses cases, my current thinking is as follows: Considering the above issues and uses cases, my current thinking is as follows:
* Store metadata in the same database as data * Store metadata in the same database as data
* Allow arbitrary key/value pairs to be associated with each message and each channel * Allow arbitrary key/value pairs to be associated with each message and group
* Initially, support the following queries: * Initially, support the following queries:
* Get the IDs of all messages with a given metadata key * Get the IDs of all messages with a given metadata key
* Ditto, also retrieving the metadata value * Ditto, also retrieving the metadata value
* Queries can be scoped to a single channel or all the client's channels * Queries can be scoped to a single group or all the client's groups
* The sync layer needs to know about dependencies between messages * The sync layer needs to know about dependencies between messages
* References between messages are encoded in the message body rather than the header * References between messages are encoded in the message body rather than the header
* References belong in the body because signatures etc may need to cover them * References belong in the body because signatures etc may need to cover them