You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking with @eras today, the automatic lookup is causing him quite a bit of latency.
Multiple solutions are possible:
Caching: look it up once and that's it. Problem: channel might get renamed, so the cached id might point to a channel that is not the same as the one that was requested.
Caching and expiring: The id is looked up and stored for some time. Unfortunately, the cache might be out of date and pointing to the wrong channel. Even worse, when it expires, it might even point to a different channel or no channel at all.
Explicit name resolution for channel: It would be nice it there was a function, that takes a channel and and looks up it's id and returns a ChannelIdchannel. Something like channel_of_channel.
I currently tend toward the latter proposal, but happy to hear input on this.
The text was updated successfully, but these errors were encountered:
After talking with @eras today, the automatic lookup is causing him quite a bit of latency.
Multiple solutions are possible:
channel
and and looks up it's id and returns aChannelId
channel
. Something likechannel_of_channel
.I currently tend toward the latter proposal, but happy to hear input on this.
The text was updated successfully, but these errors were encountered: