Pointer Monikers

A pointer moniker identifies an object that can exist only in the active or running state. This differs from other classes of monikers, which identify objects that can exist in either the passive or the active state.

Suppose, for example, an application has an object that has no persistent representation. Normally, if a client of your application needs access to that object, you could simply pass the client a pointer to the object. However, suppose your client is expecting a moniker. The object cannot be identified with a file moniker, because it isn't stored in a file, nor with an item moniker, because it isn't contained in another object.

Instead, your application can create a pointer moniker, which is a moniker that simply contains a pointer internally, and pass that to the client. The client can treat this moniker like any other. However, when the client calls IMoniker::BindToObject on the pointer moniker, the moniker code does not check the running object table (ROT) or load anything from storage. Instead, the moniker code simply calls QueryInterface on the pointer stored inside the moniker.

Pointer monikers allow objects that exist only in the active or running state to participate in moniker operations and be used by moniker clients. One important difference between pointer monikers and other classes of monikers is that pointer monikers cannot be saved to persistent storage. If you do, calling the IMoniker::Save method returns an error. This means that pointer monikers are useful only in specialized situations. You can use the CreatePointerMoniker function if you need to use a pointer moniker.

Related topics

Anti-Monikers

Class Monikers

Composite Monikers

File Monikers

Item Monikers