Should I omit database and server communication (after initial response)?
I have a project that I’m working on where a user uploads a big file which gets parsed by the backend, and then returns the data back in a friendlier format. Now I’m wondering whether I actually need a database to store it, or should I just send all the data back to the user in JSON and let JavaScript to show the data properly on button presses?
Should I omit database and server communication (after initial response)?
I have a project that I’m working on where a user uploads a big file which gets parsed by the backend, and then returns the data back in a friendlier format. Now I’m wondering whether I actually need a database to store it, or should I just send all the data back to the user in JSON and let JavaScript to show the data properly on button presses?
Should I omit database and server communication (after initial response)?
I have a project that I’m working on where a user uploads a big file which gets parsed by the backend, and then returns the data back in a friendlier format. Now I’m wondering whether I actually need a database to store it, or should I just send all the data back to the user in JSON and let JavaScript to show the data properly on button presses?
Should I omit database and server communication (after initial response)?
I have a project that I’m working on where a user uploads a big file which gets parsed by the backend, and then returns the data back in a friendlier format. Now I’m wondering whether I actually need a database to store it, or should I just send all the data back to the user in JSON and let JavaScript to show the data properly on button presses?
Pre-Processors vs Pure Web [closed]
Closed 9 years ago.
Pre-Processors vs Pure Web [closed]
Closed 9 years ago.
When developing an MVC framework, how should I be using Knockout.js?
I’m currently using the Laravel PHP MVC Framework to develop a web application; and it’s going along quite nicely. I’m very comfortable with the expectations of the framework and how my application should be structured. This is not a problem.
Semantic web and web UI impedance matching
While developing a web-application (= application with web UI) using semantic web resources / technology like RDF, OWL, SPARQL, there is constantly a feeling that at the same time semantic offers much greater possibilities to make a web more human and less “database-style” (not that I do like “parrot-style” popular with start-ups at the moment), as well as a feeling that means to create UI are somewhat limited in the face of openness of the data.
Is it possible to implement a RESTful API with a protocol other than HTTP(S)?
I was confused by the distinction between REST and HTTP, and I found this article that cleared things up for me. In summary, it explained that REST is a set of general principles for web communication, whereas HTTP is a specific application-layer internet protocol. The article pointed out that HTTP lends itself to following REST principles, but there are plenty of examples where applications violate REST while using HTTP.
when would I need state management like redux in my e commerce app?
I am new to React and web development generally so please try to understand if the question seems dumb.