- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
I've made some advances since my post. I figured out how to use the UserManager to manage users including custom attributes so I no longer have a Users SharedCollection. So I guess there are two main things I need to figure out. I'll probably figure them out eventually but here they are if anyone wants to chime in:
(1) What happens with the UserManager when there are 10,000 users in a room? Currently User A has an array of his friend's IDs which were pulled from a database.These user IDs have no real relation to AFCS; they're stored in a database specific to my application and are used to match up which user has which friends. In order to see if User C is in the room, User A must loop through all the UserDescriptors and see if the user's custom attribute "userId" matches. That way User A knows which UserDescriptor belongs to User C. So if User A has to loop through 10,000 users to find which UserDescriptors belong to his friends, that's a heavy load. I'm not sure if I can do what I need to with AFCS here.
(2) Can a user publish a node to a CollectionNode without subscribing to the CollectionNode? Likewise, can a user subscribe to a node within a CollectionNode without subscribing to the CollectionNode itself? If either of those answers are no, then that presents a scalability problem as well. Each user will be creating his own "library" node to which other users can subscribe. If the user must subscribe to the CollectionNode in order to publish a child node or subscribe to a child node, then it sounds like they would be hearing about all child nodes that get added/removed...which in my scenario could be ~10,000 different child nodes.
Am I as clear as mud? I'm sure I'll run into these answers as I move along, but if anyone has any insight that might steer my architecture beforehand, that would be fantastic. Thanks!
Aaron
Views
Replies
Total Likes