Implement Gateway Functionality about chorus HOT 5 CLOSED

maybe i could do that (i need to learn rust tho)

Feel free to go ahead, but this doesn't sound concrete enough yet for me to change the Issues' status from "Available" to "In Progress". If there's any news/you've made progress, feel free to update here!

from chorus.

maybe i could do that (i need to learn rust tho)

from chorus.

Claiming this :)

from chorus.

Outlining what the implementation should look like:

• Each Gateway object should ideally be running in its' own thread.
• It should automatically parse things like Message or Guild Events and forward the parsed message to subscribers
• Cache as little as possible; information should only be retrieved and be made ready-for-use, not stored. Consumption of this information should be handled by client implementations. Any given Event should only have one information entity assigned to it.
• Every event type could have its' own struct, which implements an observer/observable trait. A gateway connection has one object of each of these structs attached to it. An object gets updated when the gateway receives a new event which matches the object type. Some sort of function should be called when an update happens to implement observer-like behavior

from chorus.

hang on this aint finished yet

from chorus.