[
https://issues.apache.org/jira/browse/STORM-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074506#comment-14074506
]
ASF GitHub Bot commented on STORM-361:
--------------------------------------
GitHub user harshach opened a pull request:
https://github.com/apache/incubator-storm/pull/206
STORM-361. Add JSON-P support to Storm UI API.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-361-V2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/206.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #206
----
commit b0f002d65ea06c5630cab6d9c7abf95b4dfe2065
Author: Sriharsha Chintalapani <[email protected]>
Date: 2014-07-25T16:03:36Z
STORM-361. Add JSON-P support to Storm UI API.
----
> Add JSON-P support to Storm UI API
> ----------------------------------
>
> Key: STORM-361
> URL: https://issues.apache.org/jira/browse/STORM-361
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Mike Sukmanowsky
> Assignee: Sriharsha Chintalapani
> Priority: Minor
> Labels: api, ui
>
> The recent API that is being released in Storm UI with 0.9.2 is great, but
> it'd be useful if the API supported an optional {{?callback}} parameter that
> would provide a wrapped [JSON-P response|http://json-p.org/] for all
> endpoints.
> *Example:*
> {code}
> GET
> https://my-storm-head.cogtree.com/api/v1/cluster/summary?callback=myFunction
> myFunction({"stormVersion":"0.9.2-incubating","nimbusUptime":"4m
> 55s","supervisors":2,"slotsTotal":32,"slotsUsed":0,"slotsFree":32,"executorsTotal":0,"tasksTotal":0});
> {code}
> This would allow users to write clients similar to
> [elasticsearch-head|https://github.com/mobz/elasticsearch-head] (which I was
> hoping to build) where they could use a single UI to manage multiple Storm
> environments.
> Having a JSON-P {{?callback}} param would allow clients to get around
> browsers enforcing same-origin policies.
> The JSON-P site has examples of valid callback parameters:
> {code}
> functionName({JSON});
> obj.functionName({JSON});
> obj["function-name"]({JSON});
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
