Adam, It seems totally reasonable to add an additional key after authentication from some other social network; that key being named with a unique identifier from the external social network and linking to or otherwise referencing your internal user profile information. You could then choose to either keep a link from your internal profile keys to the network profile keys, or simply merge the incoming profile information from the social network into your internal version and track their identifiers separately.
-- Sean Cribbs <s...@basho.com> Developer Advocate Basho Technologies, Inc. http://www.basho.com/ On Thu, Jun 30, 2011 at 12:17 PM, Adam Lindsay <a.lind...@gmail.com> wrote: > Hi all, > > I was wondering if there's an established pattern where the value of one > key can consistently be accessed via a different key. I'm thinking of > something analogous to an HTTP 303 See Other. > > I imagine I could achieve this via link walking, but that suggests applying > a level of indirection to just about everything, or initiating all link > walks with both the direct and indirect case. > > Hmm. That's pretty abstract. How about this: > > I have a bunch of stub user profiles that could be generated via multiple > social networks. Once the user establishes their credentials on our system, > it would be good to be able to reference existing data via a new, > internally-generated user id without special-casing any link walks or > map-reduces. > > -- > Adam Lindsay > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
