From af8759a9c1d965a3220024d1857aea219d62d898 Mon Sep 17 00:00:00 2001 From: Marcos Magueta Date: Mon, 18 May 2026 12:50:25 -0300 Subject: Branching and object registry rework (#11) --- include/PermissionsManager.h | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'include/PermissionsManager.h') diff --git a/include/PermissionsManager.h b/include/PermissionsManager.h index 2db1784..6718f9f 100644 --- a/include/PermissionsManager.h +++ b/include/PermissionsManager.h @@ -58,10 +58,10 @@ namespace nt * hold of an object, since that might produce significant overhead. * * Note that the permissions systems also rely on objects with capabilities, - * so imagining the case a view (ephemeral relation) is created based on - * 3 other stored relations, while you can access the view, you cannot directly - * access the other 3 relations. You need explicit permission to create a handle - * on the others. + * so imagining the case an ephemeral relation is created based on + * 3 other stored relations, while you can access the ephemeral relation, + * you cannot directly access the other 3 relations. You need explicit + * permission to create a handle on the others. * * Here's an example tree: * /system @@ -79,7 +79,8 @@ namespace nt * /permissions * /multigroups/coffee_shop/relations/user {descriptor : [write, read]} * - * Meaning that `peter` has access to read the `user_and_order` ephemeral relation, but cannot open a handle on `user` and `order`. + * Meaning that `peter` has access to read the `user_and_order` ephemeral + * relation, but cannot open a handle on `user` and `order`. * * @param object Object being accessed. * @param connection_context Connection metadata for the caller. -- cgit v1.2.3