Issue 63110: Change to support user mediated requests in osapi
Descriptionhttps://issues.apache.org/jira/browse/SHINDIG-1065
According to osapi spec any request can be user mediated. (there is no more osapi.ui.*). Shindig to support mechanism for user mediated requests.
Changes:
- Containers can via configuration let shindig JS know which requests it want to be user mediated.
- Predefined hooks are used to pass the request to the container and get the response back.
- A new type of request, osapi.newUiRequest is defined to handle user mediated case. Even though this is in global space, it need not be visible to the developer directly. Developer uses the osapi as today.
- batch.js is modified to allow handling of user mediated requests.
- So that developer can know which request may get user mediated, every request exposes a boolean field userMediated (this is not part of standard but could be good to have something like this for future version). This would allow developers to write code like below,
var r = osapi.activites.create();
if (r.userMediated) {
// skip creating activity, as I don't want to bug the user.
} else {
r.execute();
}
[Thanks to Shishir for working with me on this change].
Patch Set 1 #Patch Set 2 : Adding missed one file uirequest.js (adding it). #Patch Set 3 : Introspect mediated methods from container. #Patch Set 4 : Fixed couple of bugs "utils" -> "util". "listMethods" -> "system.listMethods". #MessagesTotal messages: 4
|
