Feature #6019: Implement "get view" service as a REST endpoint
To match the MN.query() paradigm in which supported queryEngine types can be listed on the MN, we should list supported/registered view "engines" (aka qformats or skins).
Would probably start with all the configured skin names as a first pass, maybe throw in "xml" for good measure.
Targeting REST endpoint:
Updated by ben leinfelder over 9 years ago
- Status changed from New to Rejected
- translation missing: en.field_remaining_hours set to 0.0
Let's revisit this some other time -- not sure how this would be beneficial to clients. UIs would typically not be dynamic so as to just allow user to decide which view to utilize willy-nilly.