For the following case , there is no way to judge whether the "Open" / "Update" operation is caused by replication or not
=============================================
0. Placed replica of the same database on both Domino Server A and Domino Server B.
1. Register customer developed Extension Manager dll on both Server A and Server B. This extension manager dll includes call back functions for EM_NSFNOTEOPENEXTENDED, EM_NSFNOTEUPDATE, EM_NSFNOTEUPDATEEXTENDED
2. Update one existing document in replica on Server A, then do replication to reflect this update to the replica on Server B.
3. During the above replication, On Server A EM_NSFNOTEOPENEXTENDED is called back , and on Server B the EM_NSFNOTEUPDATE or EM_NSFNOTEUPDATEEXTENDED is called back.
4. On Server A, we can get the third parameter for NSFNoteOpenExtendedEMCallback , this parameter has the following definition in C API the document . But there is no way to judge the whether the "Open" operation is caused by replicator or not.
--------------------------------
flags - Flags that control the manner in which the note is opened. The flags are defined in OPEN_xxx (note) and may be or'ed together to combine functionality.
-------------------------------
5. On Server B , we can get the second parameter for NSFNoteUpdate or NSFNoteUpdateExtended , this parameter has the following definition in C API the document . But there is no way to judge the whether the "Update" operation is caused by replicator or not.
---------------------------------
UpdateFlags - Flags that control the manner in which the note update is done. The flags are defined in UPDATE_xxx and may be ORed together.
---------------------------------
=============================================
Customer requested HCL to provide some way to judge whether the "Open" / "Update" operation is caused by replication or not in future release.
