7650f3003e
There were a couple of issues on how we handle pinned messages: 1) Clock of the message was only checked when saving, meaning that the client would receive potentially updates that were not to be processed. 2) We relied on the client to generate a notification for a pinned message by sending a normal message through the wire. This PR changes the behavior so that the notification is generated locally, either on response to a network event or client event. 3) When deleting a message, we pull all the replies/pinned notifications and send them over to the client so they know that those messages needs updating. |
||
|---|---|---|
| .. | ||
| migrations | ||
| envelopes_monitor.go | ||
| envelopes_monitor_test.go | ||
| filter.go | ||
| filters_manager.go | ||
| filters_manager_test.go | ||
| persistence.go | ||
| processed_message_ids_cache.go | ||
| topic.go | ||
| transport.go | ||
| transport_test.go | ||