d3.js-live | Interact with d3 | Frontend Framework library
kandi X-RAY | d3.js-live Summary
kandi X-RAY | d3.js-live Summary
d3.js / live is an open-source, in progress experiment. This tool is built using React and Redux. The code block is created with react-codemirror, built on top of the awesome CodeMirror project. Other dependencies (and big props!) can be found on the github repo.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of d3.js-live
d3.js-live Key Features
d3.js-live Examples and Code Snippets
Community Discussions
Trending Discussions on d3.js-live
QUESTION
I've setup a github pages site here: http://d3js.live
This uses the github api to get gists for d3.js examples. The end look and functionality is similar to this site: http://threejs.live
I'm getting a 403 error due to my rate limit being hit. I understand that authenticating will increase my rate limit, however I'd like this site to be public. Because of this, I have a few questions:
- Any rate limit would be an issue if the traffic were to increase. Is there a reasonable scenario where I can disable the rate limit for a public page?
- If I were to authenticate with my user account, how would I create a server-side token on Github pages? I want to confirm that this token won't be visible to the client. The repo is here: https://github.com/ekatzenstein/d3.js-live
- Having the end user login with Github isn't an option. I want this to be a low-level of entry, especially for those not familiar with Github. Is it possible to tie the rate-limit per user?
Mike Bostock's bl.ocks seems to get around the rate limit but it's not clear to me how this is done.
...ANSWER
Answered 2017-Jan-09 at 15:52The best way to get around the limit is to write a simple back-end that makes the API requests to GitHub (or whoever), cache those results for some time to remain below the rate limit, and then serve all the required assets from that request to your users.
If your JavaScript is polymorphic, it should be fairly trivial to put most of what you already have in a NodeJS server.
As a general rule, this is probably what a tool like this should do, anyway. Of course, given the trade-off required, arguments could be made either way.
This is what bl.ocks seems to do, for example.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install d3.js-live
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page