About $ref attribute and relations between resources about scimd

[leogr]

The readOnly mutability for users indicates that RCF is assuming that the membership information belongs to Group, but RFC does not mandate how to implement that.
However, this implies some scalability issues (how could we return a Group's JSON representation that has millions of users?).

Furthermore, do not forget "redundancy". We're using a non-relation DB so both ways could co-exist.

[alelb]

@leogr My idea is to use listener to assign a group to the user (or an organization to a department, etc) and, in general, to assign a reference to a resource with a specific readOnly attribute when you're creating (or updating, or deleting) a resource with the referenced readWrite attribute (the members in Group).

[leodido]

Sorry @alelb remind me. When you are talking about listeners you are referring to hooks, right?

[alelb]

@leodido Yes, I am referring to hooks.

[leogr]

Assuming hooks are used in order to sync the $ref within the User's document and membership will be stored within the Group's document, isn't it?
If so, Group's document could grow indefinitely, that's a scalability issue.
However, temporarily we may go on this way, but we shall fix it later.
What do you think about that?

[alelb]

@leogr you are right.
Notice that both in the User's groups attribute and in the Group's members attribute the $ref attribute is and remains an identifier. There is no incapsulation of one document into another.