1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
//! Outbound federation events reported to
//! [`ChatBackend::on_outbound_event`](crate::ChatBackend::on_outbound_event).
//!
//! draft-atwood-jmap-chat-00 requires the server to notify other
//! participants' servers when the owner sends a Message, retracts or edits
//! one, adds or removes a reaction, reads a received Message, types, or
//! changes a group Chat or their presence. The wire methods (`Peer/deliver`
//! `message`, `edit` and `reactionUpdate`, `Peer/retract`,
//! `Peer/groupUpdate`, `Peer/receipt`, `Peer/typing`, `Peer/presence`) are
//! defined by
//! draft-atwood-jmap-chat-federation-00 and implemented outside this
//! crate. These events carry local ids (ChatContact ids, Message ids);
//! the federation layer maps them to identity strings and sends them.
//! Each `Peer/*` call names its recipient, the owner of the receiving
//! mailbox, by identity in `recipientUserId`, and goes to the peer domain
//! that is the host of that identity (draft-atwood-jmap-chat-federation-00
//! §Server-to-Server Methods, jmap-chat-spec b1cd625 L404).
//!
//! An event carries only what the stored records cannot tell the backend
//! afterwards: which members a change added, removed or re-roled, and who
//! must be told. Everything else (`body`, `name`, the full member list)
//! is read from the stored Message or Chat.
use ;
use ;
/// One outbound event the `Message/set`, `Chat/set`, `Chat/typing` or
/// `PresenceStatus/set` handler reports.
/// The `action` of a [`OutboundEvent::ReactionUpdate`]
/// (draft-atwood-jmap-chat-federation-00 §Peer/deliver `reactionUpdate`).
/// The `action` of a [`OutboundEvent::GroupUpdate`]
/// (draft-atwood-jmap-chat-federation-00 §Peer/groupUpdate).
///
/// One `Chat/set` update can report several actions. They come in this
/// order: `UpdateMetadata`, `AddMembers`, `RemoveMembers`, `UpdateRoles`,
/// then `Leave` or `Close`, so the owner's departure is last.