storm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STORM-361) Add JSON-P support to Storm UI API
Date Thu, 24 Jul 2014 00:02:44 GMT


ASF GitHub Bot commented on STORM-361:

Github user ptgoetz commented on the pull request:
    Does this combine multiple pull requests? If so, can you point them out?

> Add JSON-P support to Storm UI API
> ----------------------------------
>                 Key: STORM-361
>                 URL:
>             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|] for all endpoints.
> *Example:*
> {code}
> 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|]
(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

View raw message