Javascript XMLHttpRequest Client implementation

[andrewray]

This is an attempt to use XMLHttpRequest to make client HTTP calls from javascript programs via cohttp.

It has been lightly tested with ocaml-github where it is able to query the github API. Much still to be tested but perhaps this could be useful.

[avsm]

should be copyright you here

[avsm]

nice, I'll pull this out into so that we can have a StringCohttp pre-applied as well.

[avsm]

I've removed the Lwt from the String IO implementation (using type 'a io = 'a) and moved it into Cohttp directly so other backends can use it if they choose.

In #173

[avsm]

Would you have a simple test case for the JS backend?

[andrewray]

Does it need to be automated? I can provide a very simple test case you could run manually from a browser and, say, do a simple github query.

Automated is a bit harder. I think you can run js_of_ocaml on node.js (or it's been talked about anyway) in which case there are XHR implementations for it which may work.

[avsm]

Manual is just fine!

On 7 Sep 2014, at 13:03, Andrew Ray notifications@github.com wrote:

Does it need to be automated? I can provide a very simple test case you could run manually from a browser and, say, do a simple github query.

Automated is a bit harder. I think you can run js_of_ocaml on node.js (or it's been talked about anyway) in which case there are XHR implementations for it which may work.

—
Reply to this email directly or view it on GitHub.

[andrewray]

So here's a simple test using Cohttp_lwt_xhr to query a users github repositories and display the resulting JSON.

Note; requires Yojson to pretty print the result which may not be a dependency you want.

[avsm]

Ta! Ezjsonm is probably better since it doesn't do any obj magic -- I'll fix it up locally

On 7 Sep 2014, at 15:04, Andrew Ray notifications@github.com wrote:

So here's a simple test using Cohttp_lwt_xhr to query a users github repositories and display the resulting JSON.

Note; requires Yojson to pretty print the result which may not be a dependency you want.

—
Reply to this email directly or view it on GitHub.

[andrewray]

I'm not convinced it does - I think that was just atdgen. I was more thinking about having a dependency thats not in cohttp itself.

Actually I think theres some json stringify magic in javascript which would do this as well.

[mor1]

ityw JSON.stringify(...)

On 7 September 2014 15:16, Andrew Ray notifications@github.com wrote:

I'm not convinced it does - I think that was just atdgen. I was more
thinking about having a dependency thats not in cohttp itself.

Actually I think theres some json stringify magic in javascript which
would do this as well.

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

Richard Mortier
mort@cantab.net

[andrewray]

I think this version is a bit better. It also now prints the response headers which I think will be useful for debugging.

Some stuff still to do;

• Use async XMLHttpRequest request (important)
• May need to filter out some headers which are not allowed in browsers (on chrome they leave warnings in the log, other browsers may not be so forgiving)