This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-13
Channels
- # adventofcode (77)
- # beginners (132)
- # boot (11)
- # cider (40)
- # clara (10)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (148)
- # clojure-android (1)
- # clojure-greece (5)
- # clojure-italy (5)
- # clojure-nl (7)
- # clojure-spec (57)
- # clojure-uk (9)
- # clojurescript (115)
- # core-matrix (1)
- # cursive (3)
- # data-science (1)
- # datomic (1)
- # duct (7)
- # emacs (20)
- # fulcro (29)
- # funcool (4)
- # graphql (31)
- # instaparse (15)
- # java (1)
- # jobs (6)
- # jobs-discuss (95)
- # leiningen (2)
- # off-topic (30)
- # om (4)
- # onyx (7)
- # pedestal (6)
- # quil (4)
- # re-frame (52)
- # reagent (59)
- # rum (1)
- # spacemacs (3)
- # specter (61)
- # test-check (3)
Hey! Would you be interested in a client based directly on XMLHttpRequest as an alternative to the xhr one? I had some problems on Android with the one that uses goog.net.XhrIo on Android, maybe because of this issue: https://github.com/google/closure-library/issues/858, and I also opened another issue for another potential problem.
In general I’m just thinking there’s no reason to not just use XMLHttpRequest directly.
I’ve created a gist for now (and it’s not completely done), but I could turn it into a PR if you’re interested.
https://gist.github.com/grav/1d9ea8d5cf08f014999273be3db6dfa5
@U052XLL3A Why not creating an issue, since you did this to solve an existing issue, and link back to your gist and to the upstream issue in google closure? At least this will make it easy for other people to find your gist, and it documents the existing issue you faced. Then you can still make a PR.