Technical details on how to store refs #4
標籤
未選擇標籤
Bikeshedding
未選擇里程碑
No Assignees
1 參與者
訊息
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: jcgruenhage/git-on-matrix#4
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think the main question here is whether to prefer one larger state event over a few smaller ones. We could put all the refs into one large state event, or we could have a state event per ref with the ref being the key.
For the latter approach, we would still need to store the list of all refs somewhere, unless I missed some API to list all state keys for a given event type.
If the power level requirement was on the tuple (event_type, state_key) instead of just event_type, splitting it into multiple events would allow for setting different power level requirements per branch, but a quick read through https://matrix.org/docs/spec/client_server/r0.3.0.html#m-room-power-levels implies that this won't work.
So basically either we store an state event of the type
git.references
and an empty state key, with a content like this:Large state event:
git.references
, empty state keySmaller per ref state events
git.references
, empty state keygit.references.tag
, state keyv0.1.0
git.references.head
, state keymaster
Performance
I don't know which of those will perform better or worse, maybe homeserver implementers have a better idea here.
So I currently prefer the smaller events, most of all because that means that we can merge people pushing to different branches on different servers at the same time. If multiple people push to the same branch at the same time, we'll definitely loose all pushes except one.