| Groups | Blog | Home |
asp.net caching : Objects not Destroying
knowing when a browser closes. In fact, by the time the browser even gets the page, the server has already finished its processing and has disconnected from the client. All of your object variables will fall out of scope when the page finishes its server-side processing. The objects themselves will remain in memory until the Garbage Collector cleans up the heap. Your problem sounds more like your are caching some results somewhere and the server is reusing those results for new page requests. [quoted text, click to view] "Richard" <Richard@discussions.microsoft.com> wrote in message news:71C59AAC-9FD7-406A-B724-75C4A4BFA914@microsoft.com... > I'm running into a problem with objects not destroying when the browser > closes and is reopened. I have a custom collection that is declared public > in > a module, and instantiated elsewhere (linkbutton click event). The > collection > works fine, but when I close the browser and then I restart the web app, > the > collection is still instantiated and contains alll of the items it had > before > the browser was closed! > > I was under the impression that once the browser closes, all objects go > with > it. What I've been doing to "fix" this is in the main.aspx's pageload > event, > checking if the object is not nothing, and clearing it if it is. This is > not > limited to custom collections; I have a sortedlist class that is also > still > "active" once the browser closes and then is restarted: > > If Itinerary Is Nothing Then > Itinerary = New SortedList > Else > Itinerary.Clear() > Itinerary = Nothing > Itinerary = New SortedList > End If > > Other than the above method, how can I ensure that my objects die when the > user clicks on the close button on the browser? > > Thank you, > Richard
I'm running into a problem with objects not destroying when the browser
closes and is reopened. I have a custom collection that is declared public in a module, and instantiated elsewhere (linkbutton click event). The collection works fine, but when I close the browser and then I restart the web app, the collection is still instantiated and contains alll of the items it had before the browser was closed! I was under the impression that once the browser closes, all objects go with it. What I've been doing to "fix" this is in the main.aspx's pageload event, checking if the object is not nothing, and clearing it if it is. This is not limited to custom collections; I have a sortedlist class that is also still "active" once the browser closes and then is restarted: If Itinerary Is Nothing Then Itinerary = New SortedList Else Itinerary.Clear() Itinerary = Nothing Itinerary = New SortedList End If Other than the above method, how can I ensure that my objects die when the user clicks on the close button on the browser? Thank you,
Hi Scott, thanks for your reply. I'm not caching the sortedlist such as in a
session object, so how can it be reused by the server? It's declared in a module: Module mdlGeneral Public Itinerary As SortedList End Module Then it is instantiated and used in a click event: Private Sub btnAddToItinerary_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnAddToItinerary.Click 'Create the object if necessary. If Itinerary Is Nothing Then Itinerary = New SortedList End If 'Look for the issue id first. Add it if not already in the sortedlist. If Itinerary.ContainsKey(Session("ServiceIssueDetailIssueID").ToString) = False Then Itinerary.Add(Session("ServiceIssueDetailIssueID").ToString, Session("ServiceIssueDetailIssueDescription").ToString) End If End Sub [quoted text, click to view] "Scott M." wrote:
> The browser has absolutely nothing to do with it. The server has no way of > knowing when a browser closes. In fact, by the time the browser even gets > the page, the server has already finished its processing and has > disconnected from the client. > > All of your object variables will fall out of scope when the page finishes > its server-side processing. The objects themselves will remain in memory > until the Garbage Collector cleans up the heap. > > Your problem sounds more like your are caching some results somewhere and > the server is reusing those results for new page requests. > > > "Richard" <Richard@discussions.microsoft.com> wrote in message > news:71C59AAC-9FD7-406A-B724-75C4A4BFA914@microsoft.com... > > I'm running into a problem with objects not destroying when the browser > > closes and is reopened. I have a custom collection that is declared public > > in > > a module, and instantiated elsewhere (linkbutton click event). The > > collection > > works fine, but when I close the browser and then I restart the web app, > > the > > collection is still instantiated and contains alll of the items it had > > before > > the browser was closed! > > > > I was under the impression that once the browser closes, all objects go > > with > > it. What I've been doing to "fix" this is in the main.aspx's pageload > > event, > > checking if the object is not nothing, and clearing it if it is. This is > > not > > limited to custom collections; I have a sortedlist class that is also > > still > > "active" once the browser closes and then is restarted: > > > > If Itinerary Is Nothing Then > > Itinerary = New SortedList > > Else > > Itinerary.Clear() > > Itinerary = Nothing > > Itinerary = New SortedList > > End If > > > > Other than the above method, how can I ensure that my objects die when the > > user clicks on the close button on the browser? > > > > Thank you, > > Richard > >
Why are you declaring it in a module? That's your problem. Itinerary is
never going to be nothing as long as the web application is running. Just declare and instantiate it in the web page. If you need to persist it between different pages consider caching it or passing it between pages. [quoted text, click to view] "Richard" <Richard@discussions.microsoft.com> wrote in message news:9DCF6F55-AE2C-493C-B397-A0B8008158F5@microsoft.com... > Hi Scott, thanks for your reply. I'm not caching the sortedlist such as in > a > session object, so how can it be reused by the server? > > It's declared in a module: > Module mdlGeneral > > Public Itinerary As SortedList > > End Module > > Then it is instantiated and used in a click event: > Private Sub btnAddToItinerary_Click(ByVal sender As System.Object, > ByVal > e As System.EventArgs) Handles btnAddToItinerary.Click > > 'Create the object if necessary. > If Itinerary Is Nothing Then > Itinerary = New SortedList > End If > > 'Look for the issue id first. Add it if not already in the > sortedlist. > If > Itinerary.ContainsKey(Session("ServiceIssueDetailIssueID").ToString) = > False > Then > Itinerary.Add(Session("ServiceIssueDetailIssueID").ToString, > Session("ServiceIssueDetailIssueDescription").ToString) > End If > > End Sub > > "Scott M." wrote: > >> The browser has absolutely nothing to do with it. The server has no way >> of >> knowing when a browser closes. In fact, by the time the browser even >> gets >> the page, the server has already finished its processing and has >> disconnected from the client. >> >> All of your object variables will fall out of scope when the page >> finishes >> its server-side processing. The objects themselves will remain in memory >> until the Garbage Collector cleans up the heap. >> >> Your problem sounds more like your are caching some results somewhere and >> the server is reusing those results for new page requests. >> >> >> "Richard" <Richard@discussions.microsoft.com> wrote in message >> news:71C59AAC-9FD7-406A-B724-75C4A4BFA914@microsoft.com... >> > I'm running into a problem with objects not destroying when the browser >> > closes and is reopened. I have a custom collection that is declared >> > public >> > in >> > a module, and instantiated elsewhere (linkbutton click event). The >> > collection >> > works fine, but when I close the browser and then I restart the web >> > app, >> > the >> > collection is still instantiated and contains alll of the items it had >> > before >> > the browser was closed! >> > >> > I was under the impression that once the browser closes, all objects go >> > with >> > it. What I've been doing to "fix" this is in the main.aspx's pageload >> > event, >> > checking if the object is not nothing, and clearing it if it is. This >> > is >> > not >> > limited to custom collections; I have a sortedlist class that is also >> > still >> > "active" once the browser closes and then is restarted: >> > >> > If Itinerary Is Nothing Then >> > Itinerary = New SortedList >> > Else >> > Itinerary.Clear() >> > Itinerary = Nothing >> > Itinerary = New SortedList >> > End If >> > >> > Other than the above method, how can I ensure that my objects die when >> > the >> > user clicks on the close button on the browser? >> > >> > Thank you, >> > Richard >> >> >>
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |