Re: Sink events from window.external
From: Igor Tandetnik (itandetnik_at_mvps.org)
Date: 02/09/05
- Next message: Mark Guerrieri: "Re: Sink events from window.external"
- Previous message: Mark Guerrieri: "Re: Sink events from window.external"
- In reply to: Mark Guerrieri: "Re: Sink events from window.external"
- Next in thread: Mark Guerrieri: "Re: Sink events from window.external"
- Reply: Mark Guerrieri: "Re: Sink events from window.external"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Feb 2005 16:58:31 -0500
"Mark Guerrieri" <mguerrieri@cmsgrp.com> wrote in message
news:ewH3WruDFHA.2232@TK2MSFTNGP14.phx.gbl
> Interesting idea- but how would I know when to release the cached
> interface?
When you are being unloaded, usually when
IOleObject::SetClientSite(NULL) is called
> My COM object lives externally to the browser component,
Then make it IOleObjectWithSite::SetSite(NULL)
> and many different pages will be loaded into the browser during its
> lifetime.
Are you saying you have a COM singleton? Bad idea. Instead of giving out
the same object to every client, create a separate object for each
client, and have them forward method calls to a C++ singleton (that is
not exposed to the clients directly). Then each COM object can take care
of its event sinks.
--
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
- Next message: Mark Guerrieri: "Re: Sink events from window.external"
- Previous message: Mark Guerrieri: "Re: Sink events from window.external"
- In reply to: Mark Guerrieri: "Re: Sink events from window.external"
- Next in thread: Mark Guerrieri: "Re: Sink events from window.external"
- Reply: Mark Guerrieri: "Re: Sink events from window.external"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|