rhizi/src/client/rz_api_backend.js, branch issue593 Connective intelligence https://git.yuv.al/rhizi/atom/src/client/rz_api_backend.js?h=issue593 2015-07-23T15:40:12Z client/rz_api_backend: use rz_core.rzdoc__current__get_name (fix FIXME) 2015-07-23T15:40:12Z Alon Levy alon@pobox.com 2015-07-23T15:40:12Z urn:sha1:0f1699a38fe2a83de923acb32057ece14112672b client/rz_api_backend: add missing semicolons (Aptana Studio 3 - probably also jshint) 2015-07-23T15:28:33Z Alon Levy alon@pobox.com 2015-07-23T15:28:02Z urn:sha1:95bd7d76fa6f1c45c3384227cb437c9f21e50851 REST api: moving /load endpoints to /api/rzdoc/fetch 2015-07-06T09:33:52Z LV-426 lv-426@taproot.org.il 2015-05-23T14:24:46Z urn:sha1:9afe276a7598536cf174a4b672691acf6b7dce60 REST api: moving /graph endpoints to /api/rzdoc/ 2015-07-06T09:33:52Z LV-426 lv-426@taproot.org.il 2015-05-23T14:05:04Z urn:sha1:ba7f391b7a6fee01cd72df39a2beeffc971d6b65 add copyright and license headers for GNU AGPL v3 2015-06-04T11:22:19Z Alon Levy alon@pobox.com 2015-05-28T07:14:06Z urn:sha1:6ed6f96b1c2daa3170fdf60728edcb9080a1d3a2 rz_api_backend.js: rzdoc_search 2015-05-21T23:23:51Z LV-426 lv-426@taproot.org.il 2015-05-21T22:34:55Z urn:sha1:04deed8e233a7350e3ba16e5aaaa36f32a012adc rz_api_backend.js: propagate xhr, text_status, err_thrown 2015-05-18T15:32:30Z LV-426 lv-426@taproot.org.il 2015-05-18T13:57:30Z urn:sha1:5bb5a45705b7cc0ff58b3e175063c5908dfc0678 REST api: /graph/clone -> /api/rzdoc/clone 2015-04-29T23:05:24Z LV-426 lv-426@taproot.org.il 2015-04-29T23:05:24Z urn:sha1:b50b690d1cc249dc90c2583a1f677f77108bb0d8 add '/api' prefix to REST api calls, help differentiate from end-user HTTP paths 2015-04-29T23:04:30Z LV-426 lv-426@taproot.org.il 2015-04-29T23:04:30Z urn:sha1:0c18e3de45c432ee1ed955f0bc543d695189d0e0 client: drop rz_server_{host,port}, use document.location 2015-04-25T18:05:19Z Alon Levy alon@pobox.com 2015-04-25T13:57:10Z urn:sha1:aafae6f846f533cedc4eab1857aab97395a0be31 Since the client can be hidden from the server via multiple layers, be they load balancers, proxies or iptable rules, it is simpler to not have the server aware of those layers and have to inform the client of them, instead use information the client already has.