So just wondering if anyone can point me at the key differneces between these two ways of solving this problem:
application -> needs user data that is more than just "name, isauth" - so either something like this:
public class MyPrincipal: IPrincipal { ... has IIdentity and whatever other fields, but then you need to have accessors in your various classes...
eg: in a class/controller you need to "(this.User as MyPrincipal)" to get at the customisations.
Alternatively you can do something like this and totally ignore the "IPrincipal" thing for anything but authentication:
public class MyUserInfo{
public static Current() {... uses "IPrincipal" to get the "IDENTITY" and hten uses that as KEY to connect to DB/service get the info, cache it if needs be...
What are the pros/cons? Are there better approac ...
Go to the complete details ...