Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework Gateway #201

Open
V3L0C1T13S opened this issue Jun 16, 2023 · 0 comments
Open

Rework Gateway #201

V3L0C1T13S opened this issue Jun 16, 2023 · 0 comments

Comments

@V3L0C1T13S
Copy link
Owner

Currently, Reflectcord's Gateway consists of mostly the same structure as Spacebar's Gateway, but this has proved to be cumbersome to work with, given the infrastructure differences between Reflectcord and Spacebar. While Spacebar has to do (mostly) nothing other than filter out events and dispatch them, and respond appropriately to updates, such as membership changes, we have to worry about translation, caching data from Revolt so that we don't have to re-request information, which risks rate limits, and we have to do all of this per connection.

This issue proposes a new design that would, at the very least, share some data for the same users between connections, and also remove the giant monolithic, near 2000 line Listener.ts that handles Revolt events, and translating them to Discord ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant