From 7c773ebae018ccb9cdf4ae3f21cbe34ffb23cbfe Mon Sep 17 00:00:00 2001 From: Wim Date: Mon, 28 Aug 2017 00:33:17 +0200 Subject: Add support for editing messages across bridges. Currently mattermost/discord. Our Message type has an extra ID field which contains the message ID of the specific bridge. The Send() function has been modified to return a msg ID (after the message to that specific bridge has been created). There is a lru cache of 5000 entries (message IDs). All in memory, so editing messages will only work for messages the bot has seen. Currently we go out from the idea that every message ID is unique, so we don't keep the ID separate for each bridge. (we do for each gateway though) If there's a new message from a bridge, we put that message ID in the LRU cache as key and the []*BrMsgID as value (this slice contains the message ID's of each bridge that received the new message) If there's a new message and this message ID already exists in the cache, it must be an updated message. The value from the cache gets checked for each bridge and if there is a message ID for this bridge, the ID will be added to the Message{} sent to that bridge. If the bridge sees that the ID isn't empty, it'll know it has to update the message with that specific ID instead of creating a new message. --- bridge/config/config.go | 1 + 1 file changed, 1 insertion(+) (limited to 'bridge/config') diff --git a/bridge/config/config.go b/bridge/config/config.go index ae937915..7e6786a8 100644 --- a/bridge/config/config.go +++ b/bridge/config/config.go @@ -27,6 +27,7 @@ type Message struct { Protocol string `json:"protocol"` Gateway string `json:"gateway"` Timestamp time.Time `json:"timestamp"` + ID string `json:"id"` } type ChannelInfo struct { -- cgit v1.2.3