This would be more for a network optimization standpoint, emphasising the routing consistency and architectural handling of these components.
As it stands, only the message router components (btn-msg and pick-msg) that direct their logic to GitHub would be affected by this. And a new command can be added to manage the cache state on a particular guild or for a deployment.
This would be more for a network optimization standpoint, emphasising the routing consistency and architectural handling of these components.
As it stands, only the message router components (
btn-msgandpick-msg) that direct their logic to GitHub would be affected by this. And a new command can be added to manage the cache state on a particular guild or for a deployment.