3 ms·
Well REST allows for resources to be accessed as they are: resources. Using POST/GET query parameters implies that the server should do some actual processing o
by rcari 12y ago
Well REST allows for resources to be accessed as they are: resources. Using POST/GET query parameters implies that the server should do some actual processing on these to deliver the requested resource. With REST, you can have the resource be a static file on the server, no processing required.
- creeble 12y agoI don't think you need REST to access a static file.
- dragonwriter 12y ago> I don't think you need REST to access a static file. HTTP is a -- the prototypical -- RESTful system, and its not exactly uncommon for accessing static files on the web. REST isn't just special-purpose APIs built on top of HTTP (nor, for that matter, does it require that an API be built on top of HTTP at all.)
- rcari 12y agoSure, but how convenient it is to just generate the resource once and for all and dump it in the file system following REST semantics, thus making it useless to waste CPU cycles computing the resource contents when it's just there.
- smadge 12y agoStatic html files are the purest form of REST. What says HATEOS more that <a href=...>?