Timeline for Consuming REST services: client or server
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2016 at 22:14 | vote | accept | Arnout | ||
| Jan 24, 2016 at 10:45 | comment | added | JDT | If the frameworks' strengths match what your application needs mostly then I'd use it. And don't forget about things like logging, mail handling, user management... that you make a lot easier with a framework and that a lot of applications need to do anyway. | |
| Jan 24, 2016 at 10:39 | comment | added | Arnout | It seems like I should then stick with a server side framework. My final question: would a framework like Laravel be good for this? Isn't it overkill to use a framework that is capable of so much more while 'only' using it to make calls to the REST api and rendering the html? | |
| Jan 24, 2016 at 10:03 | history | answered | JDT | CC BY-SA 3.0 |