Reuse in-memory RDF store for consecutive PATCH requests

Open
#1,522 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

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.

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.

Dominant language
JavaScript
Stars
1.8k
Forks
308
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodeSolidServer/node-solid-server

All issues in nodeSolidServer/node-solid-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.