Skip to content

race-conditions #2

@petrubraha

Description

@petrubraha

This project won't receive any maintenance or updates (from me, other contributors are welcomed). However I will present a needed feature.

The server code was meant to run and store all the necessary information on the local RAM memory of a remote machine. It was specifically designed to bypass the need of an actual database.

The stored data is subject to change. That means multiple client request over the same set of routes would eventually "race" to update the main memory. That's not an issue. The issue is that the server has no locking mechanism for reading/writing. Locks must be implemented in the server code.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions