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
{{ message }}
This repository has been archived by the owner on Oct 26, 2019. It is now read-only.
Currently api-v1 contains all of the things, and it's very tightly coupled with core. There should be a meaningful separation between the two so other plugins/interfaces/ can be added by server hosts easily, while keeping everything in sync.
Ideally we'd want some multiprocess support so we can have like millions of people online and do 0-downtime server upgrades (I mean, I assume that's how it works! not an expert. But we need to be able to do that, anyway.) in the long term.
Currently api-v1 contains all of the things, and it's very tightly coupled with core. There should be a meaningful separation between the two so other plugins/interfaces/ can be added by server hosts easily, while keeping everything in sync.
Ideally we'd want some multiprocess support so we can have like millions of people online and do 0-downtime server upgrades (I mean, I assume that's how it works! not an expert. But we need to be able to do that, anyway.) in the long term.
Idea:
https://docs.google.com/drawings/d/1xq_F4mUoF0gsE_q5LW26fA2pElgTBf2zOKKkQaKq6AU/view
The text was updated successfully, but these errors were encountered: