Represent channels and messages using a split "History" and "Snapshot" model.

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.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/token/app.rs b/src/token/app.rs
index 030ec69..5c4fcd5 100644
--- a/src/token/app.rs
+++ b/src/token/app.rs
@@ -127,7 +127,7 @@ impl<'a> Tokens<'a> {
         tx.commit().await?;
 
         for event in tokens.into_iter().map(event::TokenRevoked::from) {
-            self.tokens.broadcast(&event);
+            self.tokens.broadcast(event);
         }
 
         Ok(())
@@ -139,7 +139,7 @@ impl<'a> Tokens<'a> {
         tx.commit().await?;
 
         self.tokens
-            .broadcast(&event::TokenRevoked::from(token.clone()));
+            .broadcast(event::TokenRevoked::from(token.clone()));
 
         Ok(())
     }