C
Chan
In MS' TimeTracker sample app, a middle-tier component BLL has a class
named TimeEntry. It's used in TimeEntry.aspx to remember a certain
state of an entry.
I must have missed something but just can not find a clue on its life
scope, as the more request for the page, the more resources used up
for this and eventually may impact the system. So, can any expert
explain,
1> what's the life scope of TimeEntry, and when it will be scraped?
2> how do we tell the GC not to touch it?
Thanks!
named TimeEntry. It's used in TimeEntry.aspx to remember a certain
state of an entry.
I must have missed something but just can not find a clue on its life
scope, as the more request for the page, the more resources used up
for this and eventually may impact the system. So, can any expert
explain,
1> what's the life scope of TimeEntry, and when it will be scraped?
2> how do we tell the GC not to touch it?
Thanks!