| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Represent channels and messages using a split "History" and "Snapshot" model. | Owen Jacobson | 2024-10-03 |
| | | | | | | | This separates the code that figures out what happened to an entity from the code that represents it to a user, and makes it easier to compute a snapshot at a point in time (for things like bootstrap). It also makes the internal logic a bit easier to follow, since it's easier to tell whether you're working with a point in time or with the whole recorded history. This hefty. | ||
| * | Track event sequences globally, not per channel. | Owen Jacobson | 2024-10-01 |
| Per-channel event sequences were a cute idea, but it made reasoning about event resumption much, much harder (case in point: recovering the order of events in a partially-ordered collection is quadratic, since it's basically graph sort). The minor overhead of a global sequence number is likely tolerable, and this simplifies both the API and the internals. | |||
