Add JSONP support for monitoring routes

[devfacet]

See #100

[pkieltyka]

Also, the response content-type for jsonp is application/javascript

[devfacet]

Damn finally...

[pkieltyka]

probably better off just using r.URL.Query().Get("callback") as you only need to check the URL query params

[devfacet]

@pkieltyka : done, thank you 😄

[derekcollison]

If not done already could someone update README to reflect the JSONP functionality?

[devfacet]

@derekcollison : What kind of information you want to see in README related to this PR?

P.S.: Personally I'm thinking that README.md should be very lightweight for first impression. JSONP is a low level detail which should be in another file. Perhaps in a dedicated monitoring documentation or a file named API.md in root folder which contains everything about gnatsd with all the details.

[derekcollison]

The README has a monitoring section, just add a one liner that says it
supports JSONP via the callback arg and a simple example. No need for each
endpoint, just one IMO..

On Tue, Aug 18, 2015 at 5:29 PM, Fatih Cetinkaya notifications@github.com
wrote:

@derekcollison https://github.com/derekcollison : What kind of
information you want to see in README related to this PR?

P.S.: Personally I'm thinking that README.md should be very lightweight
for first impression. JSONP is a low level detail which should be in
another file. Perhaps in a dedicated monitoring documentation or a file
named API.md in root folder which contains everything about gnatsd with
all the details.

—
Reply to this email directly or view it on GitHub
#103 (comment).

[derekcollison]

This good to go?

[devfacet]

I just added a note to README about JSONP. I think it is okay to go...