Re: How to keep my com exe alive?
- From: "shaji" <shajiparemmal@xxxxxxxxx>
- Date: 9 Mar 2006 02:40:21 -0800
Hi Igor,
Thanks for this.
Overriding PostMessageLoop works when the Module.Lock() is not used. If
I use the Lock() and does not call Unlock() anywhere, the exe will go
down only when the system shuts down, right?
Now, what I am looking for is a way to trap the WM_QUIT that is sent to
my exe when the system shuts down and save my internal data at that
time.
Is that possible? If yes, how can I do it?
Thanks,
Shaji.
Igor Tandetnik wrote:
"shaji" <shajiparemmal@xxxxxxxxx> wrote in message
news:1141820689.598628.253300@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
1. I want to keep my com exe (just one ATL COM object - free threaded
- dual interface) running even after all the clients have quit. But I
don't want to make it a service.
Call _Module.Lock() to keep yourself alive. Call Unlock() when you
finally decide it's time to terminate.
2. When the exe shuts down, I want to save some internal data (in
fact, an stl list) onto the disk so that it can be read when next
time the exe starts up
Override PostMessageLoop in your CAtlExeModule-derived class.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: How to keep my com exe alive?
- From: Alexander Nickolov
- Re: How to keep my com exe alive?
- From: Igor Tandetnik
- Re: How to keep my com exe alive?
- References:
- How to keep my com exe alive?
- From: shaji
- Re: How to keep my com exe alive?
- From: Igor Tandetnik
- How to keep my com exe alive?
- Prev by Date: Re: VC++6 to VS2003 woes...
- Next by Date: Re: How to keep my com exe alive?
- Previous by thread: Re: How to keep my com exe alive?
- Next by thread: Re: How to keep my com exe alive?
- Index(es):
Relevant Pages
|
Loading