Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

support for .unprovide #78

Open
martinheidegger opened this issue Feb 6, 2019 · 0 comments
Open

support for .unprovide #78

martinheidegger opened this issue Feb 6, 2019 · 0 comments
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked

Comments

@martinheidegger
Copy link

As the documentation around .provide is a little thin I am guessing it announces the availability of a resource identified through a key(buffer). Somehow it seems necessary to have a corresponding opposite .unprovide in case that resource is no-longer available, triggering peers to remove one-self from the provider list.
@vasco-santos vasco-santos added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue exp/expert Having worked on the specific codebase is important P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked labels Feb 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinheidegger @vasco-santos