Web framework: Difference between revisions

Revision as of 05:11, 1 August 2023

Revision as of 03:40, 13 August 2023

Line 43:

===General-purpose website frameworks===

Web frameworks must function according to the architectural rules of browsers and [[communication protocol|protocols]] such as [[Hypertext Transfer Protocol|HTTP]], which is [[Stateless protocol|stateless]]. Webpages are served up by a [[server (computing)|server]] and can then be modified by the browser using [[JavaScript]]. Either approach has its advantages and disadvantages.<ref>{{citationCite web needed|date=January2023-08-12 2017|title=Top 10 Web Development Frameworks in 2023 - Real Flippa |url=https://realflippa.com/top-10-web-development-frameworks-in-2023/ |access-date=2023-08-13 |language=en-US}}</ref>

Server-side page changes typically require that the page be refreshed, but allow any language to be used and more computing power to be utilized. Client-side changes allow the page to be updated in small chunks which feels like a desktop application, but are limited to JavaScript and run in the user's browser, which may have limited computing power. Some mix of the two is typically used.<ref>{{Cite web|url=https://spin.atomicobject.com/2015/04/06/web-app-client-side-server-side/|title=Web Application Architecture – Client-Side vs. Server-Side|last=KLIMUSHYN|first=Mel|website=Atomic Spin|date=6 April 2015|access-date=2016-03-06}}</ref> Applications which make heavy use of JavaScript and only refresh parts of the page, are called [[single-page application]]s and typically make use of a client-side JavaScript web framework<ref>{{Cite web |date=2023-08-12 |title=Top 10 Web Development Frameworks in 2023 - Real Flippa |url=https://realflippa.com/top-10-web-development-frameworks-in-2023/ |access-date=2023-08-13 |language=en-US}}</ref> to organize the code.{{citation needed|date=January 2017}}

====Server-side====