什么是谓词？(What is a predicate?)

 有几种方法，有不同的权衡。 可能最常见的两个是： 
 
 在需要时从后备存储中获取对象。 基本上在Page_Load您可以使用您拥有的标识符获取所需的数据： 
 
protected void Page_Load(object sender, EventArgs e)
{
    var player = SomePlayerRepository.GetPlayer(User.Identity.Name);
    txtFirstName.Text = player.FirstName;
    // etc.
}
 
 SomePlayerRepository可以以多种方式实现。 例如，它可以包括内存中缓存，因此它不必一次又一次地访问数据库。 
 
 要么： 
 
 最初获取对象并将其存储在应用程序本地的某个位置。 这与上面提到的“缓存”非常相似，它只是更明确，更少抽象。 例如，您可以将其存储在Session ： 
 
var exists = login.ValidateLogin();
if (exists == 1)
{         
    Session["CurrentPlayer"] = SomePlayerRepository.GetPlayer(txtUserName.Text);
    FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, false);
}
 
 然后在Page_Load ： 
 
protected void Page_Load(object sender, EventArgs e)
{
    var player = (Player)Session["CurrentPlayer"];
    txtFirstName.Text = player.FirstName;
    // etc.
}
 
 其他选项可能包括将其存储在用户的cookie中。 
 
 我个人更喜欢第一种方法，因为它分离了提取/缓存/等。 来自页面逻辑的逻辑，为要使用的页面提供通用的应用程序范围（或可能是域范围的）接口。 这解耦了逻辑的不同组件，允许您以最小的努力修改/替换组件。 

There are a couple of approaches, with varying trade-offs. Probably the two most common are:
 
Fetch the object from backing storage when you need it. Basically on Page_Load you'd get the data you need using the identifier you have:
 
protected void Page_Load(object sender, EventArgs e)
{
    var player = SomePlayerRepository.GetPlayer(User.Identity.Name);
    txtFirstName.Text = player.FirstName;
    // etc.
}
 
The SomePlayerRepository can be implemented in any number of ways. It can include in-memory caching so that it doesn't have to hit the database over and over again, for example.
 
Or:
 
Fetch the object initially and store it somewhere local to the application. This is very similar to the "caching" mentioned above, it's just more explicit and less abstracted. For example, you might store it in Session:
 
var exists = login.ValidateLogin();
if (exists == 1)
{         
    Session["CurrentPlayer"] = SomePlayerRepository.GetPlayer(txtUserName.Text);
    FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, false);
}
 
then in Page_Load:
 
protected void Page_Load(object sender, EventArgs e)
{
    var player = (Player)Session["CurrentPlayer"];
    txtFirstName.Text = player.FirstName;
    // etc.
}
 
Other options could include storing it in the user's cookie.
 
Personally I prefer the first approach because it separates the fetching/caching/etc. logic from the page logic, providing a common application-wide (or domain-wide perhaps) interface for the pages to use. This decouples different components of logic allowing you to modify/replace components with minimal effort.