Allows clients to control which fields will be sent in the API response. The idea is based on a recipe described in the official documentation, Dynamically modifying fields, adapted to allow API users to specify fields via GET request query parameters.
Doing the filtering server-side instead of client-side can have advantages:
Fewer bytes down the wire = snappier ajax for your webapps
Less backend server load if expensive-to-serialize fields go unneeded
For thin clients; a better choice if client-side is a dumb/low-power device
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4