8 ms·
A server that only serves static files. It doesn't enable the use of dynamic content like CGI[1]. Compare this to something like Apache or nginx. Both can serve
by sehrope 13y ago
A server that only serves static files. It doesn't enable the use of dynamic content like CGI[1]. Compare this to something like Apache or nginx. Both can serve static files but also support a number of ways of either directly running scripts (ex: mod_perl or mod_php in Apache) or proxying to other servers that handle dynamic content.
[1]: https://en.wikipedia.org/wiki/Common_Gateway_Interface https://en.wikipedia.org/wiki/Common_Gateway_Interface
- deleted 13y ago[deleted]
- ds9 13y agoOK, then, sorry if I'm being dense, but how can it be "for serving web apps"? App seems an odd term for a site consisting of only static files.
- packetslave 13y agoPerhaps you've heard of this new language, JavaScript?
- ds9 13y agoStill not much of an app unless the JS does AJAX, but then it's talking to a server that's running some dynamic process, maybe with DB access etc. - right?
- Isofarro 13y agoNot necessarily. You can make an ajax request to a static resource. The server doesn't have to be a dynamic process. Static resources are just files. A client-side JavaScript Twitter could be done this way. Every tweet, or timeline can be pre-baked into a static json file, and ajaxed in. Twitter can then be simplified to a backend application that updates these files. Granted, tweeting is a separate matter; that requires an endpoint that processes data.
- WhitneyLand 13y agoCross-domain REST is the big win. MongoLab, APIs, Widgets, etc.