Asynchronous Event Methods
Asynchronous Event Methods
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Microsoft® Exchange provides asynchronous event notifications by calling the IExStoreAsyncEvents Interface methods in the following table.
| Name | Description |
|---|---|
| OnSave Method | Called when an item is saved to the Exchange store. |
| OnDelete Method | Called when an item is deleted from the Exchange store. |
When you process an asynchronous event, Exchange processes the return value. Returning S_OK indicates that the event notification was handled successfully. Returning S_PENDING indicates that you are handling the Exchange notification in a separate process. When you return S_PENDING, you must notify Exchange (from the separate process) when you have finished handling the Exchange notification by calling the Completed Method.
See the IAsyncNotify Interface for information about processing an asynchronous event in a Component Object Model (COM) object.
Loop Recursion
An asynchronous event method can modify the item that caused the event notification, which, in turn, can fire an event for the same item. This causes a recursive event loop. The event sink must ensure that looping does not occur.
Related Topics
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.