[jira] [Updated] (STORM-361) Add JSON-P support to Storm UI API

["Rick Kellogg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-361:
-------------------------------
    Component/s: storm-core

> Add JSON-P support to Storm UI API
> ----------------------------------
>
>                 Key: STORM-361
>                 URL: https://issues.apache.org/jira/browse/STORM-361
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>    Affects Versions: 0.9.2-incubating
>            Reporter: Mike Sukmanowsky
>            Assignee: Sriharsha Chintalapani
>            Priority: Minor
>              Labels: api, ui
>             Fix For: 0.9.3
>
>
> 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.3.4#6332)