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

Feature request: Refactoring to decouple client and server code bases #3183

Open
almereyda opened this issue Jan 26, 2020 · 1 comment
Open

Comments

@almereyda
Copy link

The current client implementation is based on Node.js and called the web app. Since the project builds on LDP, it appears interesting to consider, if a decoupled web app could run on this Java server implementation, but also on a general LDP interface like the one Solid provides.

Decoupling the client from the server code can help remove entry barriers for third-party developers that are not able to work with Java, and allows them to focus on the user-facing JavaScript components of the Web of Needs platform, if participatory development is desired.

This came up after discussing the Web of Needs project from perspective of the Value Flows project valueflows/forum.valueflo.ws#128 (comment) / https://valueflo.ws, which has a working Solid implementation at https://app.solidbase.info / https://lab.allmende.io/solidbase/solidbase

@fkleedorfer
Copy link
Member

Thanks for the hint, i agree with the general idea. However, WoN is not a LDP application, wr only borrowed some concepts like containers and paging. That said, participatory development is desired and we are interested in making things easier. Also, we've been looking into valueflows again lately and it looks like it could ve a very good match for what we want to achieve, sort of, the next-higher up layer on top of WoN.

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

2 participants