clockworklabs / clockworklabs/SpacetimeDB
Server-side subscriptions?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
It would be great if reducers could be scheduled whenever a change is detected in a query, just like on the client side. This behaviour is not easily replicable by polling with periodically scheduled reducers either, as far as I can tell change detection is not exposed on the server-side Rust crate like it is on some other ECS systems (Like Changed<T> in Bevy).
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
Start by surveying the server-side Rust crate's reducer scheduling and query execution paths, then compare them with the client-side subscription behavior mentioned in the issue. Determine where query change detection could be exposed and define tests showing that reducers are scheduled when relevant query results change, without relying on polling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100