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

Detaching the user interface from the back-end #181

Open
realies opened this issue Oct 3, 2017 · 0 comments
Open

Detaching the user interface from the back-end #181

realies opened this issue Oct 3, 2017 · 0 comments

Comments

@realies
Copy link
Contributor

realies commented Oct 3, 2017

The current web system is processing data inline within the graphical user interface, meaning that if an element in the middle of the page contains particular data that takes some time to be processed, or the returning command is taking some time to respond, the complete render of the web page will be delayed by that amount of time.

The current approach is not a good practice when having to wait for multiple or time-consuming commands to return their value, which is the cause of loading delays that we have all seen.

Should there be a roadmap for separating the concerns of front and back-ends for future iterations of unRAID? Unifying back-end functionality in classes and modules instead of relying on separate script files as it is right now as well as consuming the back end with a modern front-end framework instead of parsing inline will improve the speed, performance, responsiveness, and development of the web system.

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

No branches or pull requests

1 participant