mandatoryprogrammer / mandatoryprogrammer/sonar.js
Memoize the checking of resources on hosts to save on network requests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 551
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
sonar should never make two requests for a resource on a host. It should keep a running table for resources that it knows exist/doesn't exist and then check the table before potentially wasting time with another network operation.
For example:
``` js
var resource_table = {
'192.168.1.2': ['/resource.css', '/resource.png', '/resource.jpg' ],
'192.168.1.3': ['/resource.css', '/other.png', '/example.jpg' ],
}
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue, so first locate the code that requests resources from hosts and trace how repeated checks are initiated. Done means maintaining per-host knowledge of existing and missing resources and avoiding a second network request for a resource already recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100