interface enables containers and other interested objects to receive
notifications of data changes, view changes, and compound-document changes occurring in
objects of interest. Container applications, for example, require such
notifications to keep cached presentations of their linked and embedded objects
For an advisory connection to exist, the object that is to receive
notifications must implement IAdviseSink
, and the objects in which it is interested must implement one or more of the
, or IViewObject::SetAdvise
. Objects implementing IOleObject
must support all of these methods.
As shown in the following table, an object that has implemented an advise sink
registers its interest in receiving certain types of notifications by calling
the appropriate method:
|Call This Method
||To Register for These Notifications
||When a document is saved, closed, or renamed.
||When a document's data changes.
||When a document's presentation changes.
When an event occurs that applies to a registered notification type, the
object application calls the appropriate IAdviseSink
method. For example, when an embedded object closes, it calls the IAdviseSink::OnClose
method to notify its container. These notifications are asynchronous,
occurring after the events that trigger them
When to Implement
Objects, such as container applications, compound documents, and client sites
to receive notification of changes in data, presentation, name, or state of
their linked and embedded objects. Implementors register for one or more types
of notification, depending on their needs.
Notifications for an embedded object originate in the object application and
flow to the container by way of the object handler. If the object is a linked
object, the OLE link object intercepts the notifications from the object handler
and notifies the container directly. All containers, the object handler, and
the OLE link object register for OLE notifications. The typical container also
registers for view notifications. Data notifications are usually sent to the OLE
link object and object handler.
When to Use
Objects call IAdviseSink
to notify other objects with whom they have an advisory connection of changes
in data, view, name, or state.
Making synchronous calls within asynchronous methods is not valid, so you
cannot make synchronous calls within any of the the IAdviseSink
interface's methods. For example, an implementation of IAdviseSink::OnDataChange
cannot contain a call to IDataObject::GetData
Methods in Vtable Order
||Returns pointers to supported interfaces.
||Increments reference count.
||Decrements reference count.
||Advises that data has changed.
||Advises that view of object has changed.
||Advises that name of object has changed.
||Advises that object has been saved to disk.
||Advises that object has been closed.
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages