You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trust of KeyVal , is only usefull if we filter some query and value propagation.
Currently this is only possible with accept rules (see wotaccess of fs example) for trusted incomming peer.
We need to add rules over accept_query_kv, accept_query_peer, accept_kv (accept becomes accept_peer).
we need that get_closest of route will also be filtered over query trust (we want our first query to be to peer of related trust (especialy when using multitrust see[https://github.com/parameterization of peer prio and multitrust #25]). We may plug a rules to filter results and recall get_closest with filtered result in parameter (there is already this param to avoid loops), and repeat until no more result or enough peer.
This will be inefficient when 'route' already did some filtering (for exemple a route which use priority related to trust do the filtering already when get closest is done). Therefore this loop will be in accept closest rules (so that when we trust our route we just change this rule).
The text was updated successfully, but these errors were encountered:
Trust of KeyVal , is only usefull if we filter some query and value propagation.
Currently this is only possible with accept rules (see wotaccess of fs example) for trusted incomming peer.
This will be inefficient when 'route' already did some filtering (for exemple a route which use priority related to trust do the filtering already when get closest is done). Therefore this loop will be in accept closest rules (so that when we trust our route we just change this rule).
The text was updated successfully, but these errors were encountered: