rest-proxy service as a service

[apetro]

Idea: Make hosted rest-proxy a feature of the MyUW frame-based app hosting platform.

Bigger picture: enabling frame-based applications where the part running "in MyUW' is entirely

1. configuration at the httpd layer (as in, Shibboleth SP configuration)
2. static files served as is to the browser (that is, the client-side AngularJS/JavaScript/HTML5 application that runs in the end user's browser)
3. configuration at the application-in-MyUW layer

and is not any application-specific code running server-side "in MyUW'.

So instead of a frame-based app providing an instance of a rest-proxy, it provides a JSON file fulfilling a semantically versioned configuration API. MyUW the hosting platform reads that configuration file associated with the frame-based app and provides a platform-provided instance of rest-proxy fulfilling the configuration.

(The proxy would typically proxy to a back-end running elsewhere, in Shared Hosting or otherwise).

A similar idea for platform-provided KeyValueStore-as-a-service.

The modules running "in MyUW" get less individually custom, more supportable, simpler. They're just static resources to be served to the client and configuration, no server-side custom code.