logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

RE: Support for user properties: msg#00073

Subject: RE: Support for user properties
> From: liveuser-bounces-jG1DcbwcvVYUuug7z7PF4w@xxxxxxxxxxxxxxxx 
> [mailto:liveuser-
> bounces-jG1DcbwcvVYUuug7z7PF4w@xxxxxxxxxxxxxxxx] On Behalf Of Jeremy Mikola
 
> both explanations were quite helpful, thanks.
> 
> > Now data like Name, First Name, Phone, Email, usually belong
> > to the auth container because this data is not related to the
> > application but to the account. I, for example, put name, and
> > email in the auth users table.
> >
> > On the other hand anything that is application specific, like the
> > user being a manager for a CMS is application specific because
> > he may have another position in an other app.
> 
> in the event that you're adding fields to the auth container, does
that
> entail extending liveuser's api to query for such properties, or would
you
> be using your own separate code to fetch those extra fields for your
> application?

I would only fetch fields that relate to auth in the auth container and
perm in the perm container ... fetching other data might be more
efficient but not very clean.

Regards,
Lukas


<Prev in Thread] Current Thread [Next in Thread>