philip/ubisync
1
0
Fork 0
Code Issues 15 Pull requests Projects Releases Packages Wiki Activity

Implement pot sharing #4

New issue
Open
opened 2024-01-24 00:00:34 +00:00 by philip · 0 comments
philip commented 2024-01-24 00:00:34 +00:00
Owner
Copy link

A node should know which other nodes are participating in a pot and pro- and reactively exchange its contents.

  • Store list of "interested nodes"/participants
  • Upon updates, attempt to directly push them to the nodes to which there currently is an existing communication channel
  • Periodically ask participating nodes for updates in shared pots
  • Check permission for each requested share
A node should know which other nodes are participating in a pot and pro- and reactively exchange its contents. - [ ] Store list of "interested nodes"/participants - [ ] Upon updates, attempt to directly push them to the nodes to which there currently is an existing communication channel - [ ] Periodically ask participating nodes for updates in shared pots - [ ] Check permission for each requested share
philip added this to the v1 milestone 2024-01-24 00:00:34 +00:00
philip added the
Kind/Feature
 label 2024-01-24 00:00:34 +00:00
philip added the
crate/ubisync
 label 2024-02-11 14:24:16 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
crate/ubisync

This issue relates to the ubisync crate, which provides an implementation of a ubisync node.

  
crate/ubisync-lib

This issue relates to the ubisync-lib crate, which defines common types and traits useful to node and app developers

  
crate/ubisync-sdk

This issue relates to the ubisync-sdk crate, which provides useful abstractions of the HTTP API for app developers

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
crate/ubisync
crate/ubisync-lib
crate/ubisync-sdk
Milestone
Clear milestone
No items
No milestone
v1
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: philip/ubisync#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?