Application Ending : Save the static object in a File to reload it alter !

[Shanli RICHEZ]

I'm using ASP.NET and quite a lot of object in memory instead of a database.

The question is that I tried to save the data, serialize them in a XML file
to save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Scott Allen]

Where do you keep references to the data? In Session?

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Sat, 27 Nov 2004 09:18:25 +0100, "Shanli RICHEZ" <sh****@noos.fr>
wrote:

I'm using ASP.NET and quite a lot of object in memory instead of a database.

The question is that I tried to save the data, serialize them in a XML file
to save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Shanli RICHEZ]

No in static hashTable or ArrayList declare in the classes !

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:r7********************************@4ax.com...

Where do you keep references to the data? In Session?

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Sat, 27 Nov 2004 09:18:25 +0100, "Shanli RICHEZ" <sh****@noos.fr>
wrote:

I'm using ASP.NET and quite a lot of object in memory instead of a database.
The question is that I tried to save the data, serialize them in a XML fileto save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Paul Glavich [MVP - ASP.NET]]

Why dont you save the information to the database on first created and when
it changes (ie. pro-actively) rather than trying to save it when the
application ends. That way, the database always contains a reflection of
what is held in memory and reloading it from where you left off is trivial

--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

I'm using ASP.NET and quite a lot of object in memory instead of a database.
The question is that I tried to save the data, serialize them in a XML file to save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Shanli RICHEZ]

The static object contains counter, statistique per user that can be
increment/decrement 15,000 times an hour.

That's why I do not save them in the database because it will take to much
ressource.

I could save them every minute with a timer, but the problem is that when I
shut down the machine I lose the lastest information. So I wanted to catch
the event n application end to save them.

Shanli




"Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

Why dont you save the information to the database on first created and when it changes (ie. pro-actively) rather than trying to save it when the
application ends. That way, the database always contains a reflection of
what is held in memory and reloading it from where you left off is trivial

--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

I'm using ASP.NET and quite a lot of object in memory instead of a

database.

The question is that I tried to save the data, serialize them in a XML

file

to save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Paul Glavich [MVP - ASP.NET]]

Then what about the finaliser for the object? It will only be garbage
collected when the apDomain is being unloaded and it keeps that logic within
the object itself.

--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:OU**************@TK2MSFTNGP14.phx.gbl...

The static object contains counter, statistique per user that can be
increment/decrement 15,000 times an hour.

That's why I do not save them in the database because it will take to much
ressource.

I could save them every minute with a timer, but the problem is that when I shut down the machine I lose the lastest information. So I wanted to catch
the event n application end to save them.

Shanli




"Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

Why dont you save the information to the database on first created and

when

it changes (ie. pro-actively) rather than trying to save it when the
application ends. That way, the database always contains a reflection of
what is held in memory and reloading it from where you left off is trivial
--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

I'm using ASP.NET and quite a lot of object in memory instead of a

database.

The question is that I tried to save the data, serialize them in a XML

file

to save them when the application is ending.

event : Application_End in Global.asax.

But the object are not accesible from there so I can't save them.

Any idea ???

Thanks.

[Shanli RICHEZ]

That's seems to be a good idea.

Thanks.
"Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
message news:%2******************@TK2MSFTNGP09.phx.gbl...

Then what about the finaliser for the object? It will only be garbage
collected when the apDomain is being unloaded and it keeps that logic within the object itself.

--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:OU**************@TK2MSFTNGP14.phx.gbl...

The static object contains counter, statistique per user that can be
increment/decrement 15,000 times an hour.

That's why I do not save them in the database because it will take to much

ressource.

I could save them every minute with a timer, but the problem is that when

I

shut down the machine I lose the lastest information. So I wanted to

catch the event n application end to save them.

Shanli




"Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
message news:%2****************@tk2msftngp13.phx.gbl...

Why dont you save the information to the database on first created and

when

it changes (ie. pro-actively) rather than trying to save it when the
application ends. That way, the database always contains a reflection of what is held in memory and reloading it from where you left off is

trivial
--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...
> I'm using ASP.NET and quite a lot of object in memory instead of a
database.
>
> The question is that I tried to save the data, serialize them in a XML file
> to save them when the application is ending.
>
> event : Application_End in Global.asax.
>
> But the object are not accesible from there so I can't save them.
>
> Any idea ???
>
> Thanks.
>
>
>

[Scott Allen]

What happens in Application_End that prevents the save from working?

I'd shy away from the finalizer because there is no guarantee the
finalizer will run. There is one thread dedicated to running
finalizers and the runtime can timeout an operation on the thread to
prevent the thread from hanging.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Sun, 28 Nov 2004 12:19:07 +0100, "Shanli RICHEZ" <sh****@noos.fr>
wrote:

That's seems to be a good idea.

Thanks.
"Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
message news:%2******************@TK2MSFTNGP09.phx.gbl...

Then what about the finaliser for the object? It will only be garbage
collected when the apDomain is being unloaded and it keeps that logic

within

the object itself.

--
- Paul Glavich
Microsoft MVP - ASP.NET
"Shanli RICHEZ" <sh****@noos.fr> wrote in message
news:OU**************@TK2MSFTNGP14.phx.gbl...

> The static object contains counter, statistique per user that can be
> increment/decrement 15,000 times an hour.
>
> That's why I do not save them in the database because it will take tomuch > ressource.
>
> I could save them every minute with a timer, but the problem is thatwhen

I

> shut down the machine I lose the lastest information. So I wanted to

catch > the event n application end to save them.
>
> Shanli
>
>
>
>
>
>
>
>
>
>
> "Paul Glavich [MVP - ASP.NET]" <gl**@aspalliance.com-NOSPAM> wrote in
> message news:%2****************@tk2msftngp13.phx.gbl...
> > Why dont you save the information to the database on first created and
> when
> > it changes (ie. pro-actively) rather than trying to save it when the
> > application ends. That way, the database always contains a reflectionof > > what is held in memory and reloading it from where you left off is

trivial

> >
> > --
> > - Paul Glavich
> > Microsoft MVP - ASP.NET
> >
> >
> > "Shanli RICHEZ" <sh****@noos.fr> wrote in message
> > news:%2******************@TK2MSFTNGP09.phx.gbl...
> > > I'm using ASP.NET and quite a lot of object in memory instead of a
> > database.
> > >
> > > The question is that I tried to save the data, serialize them in aXML > > file
> > > to save them when the application is ending.
> > >
> > > event : Application_End in Global.asax.
> > >
> > > But the object are not accesible from there so I can't save them.
> > >
> > > Any idea ???
> > >
> > > Thanks.
> > >
> > >
> > >
> >
> >
>
>