nodeSolidServer / nodeSolidServer/node-solid-server
Reuse in-memory RDF store for consecutive PATCH requests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
When you do two consecutive write operations on the same resource, the data has to go to disk and go back into memory in-between the first and the second request. If there is no time for that, the second PATCH fails with because the resource is locked.
This behaviour could be improved by reusing the in-memory RDF store across requests.
Contributor guide
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 or tests are identified in the issue. Start by tracing PATCH request handling and the lifecycle of the in-memory RDF store; done means consecutive writes to the same resource can reuse in-memory data without the second PATCH failing because the resource is locked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100