Cool, so what you are saying is that each user would have 2 channels a 
'Messages' channel and a 'Relationship' channel? In terms of scale there 
wouldn't be an issue if say you had 100k users which would mean 200k 
channels?

I am a little confused about this sentence you wrote.


*(I’m separating the two kinds of channels so that following someone 
doesn’t automatically show you who they’re following or being followed by.)*

Did you mean to say that by following someone they don't automatically see 
your messages? If as you said the sync function is adding {“user”: “A”, 
follows: “B”} to both A and B's 'relationship' channel. Wouldn't they be 
able to see who followers them etc but if you only grant B access to A's 
'message' channel, B would only see A's messages and A wouldn't see B's 
messages?

Thanks
Joel


On Wednesday, April 13, 2016 at 12:46:11 AM UTC+10, Jens Alfke wrote:
>
>
> On Apr 11, 2016, at 6:23 PM, Joel W <[email protected] <javascript:>> 
> wrote:
>
> Thanks Jens, this make sense for user A follows B and C. How would handle 
> so you could see User A is followed by C and D? Would you need to have a 
> relationship doc type, that defines the relationship between each user and 
> this gets added to the channel of each user in the relationship?
>
>
> That would work.  Something like {“user”: “A”, follows: “B”}. The sync 
> function would add this to both A and B’s ‘relationships’ channels, and 
> grant B access to A’s ‘messages’ channel. (I’m separating the two kinds of 
> channels so that following someone doesn’t automatically show you who 
> they’re following or being followed by.)
>
> —Jens
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/c2ba6bd0-e972-46b2-9784-81ec38d3c440%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to