Moniker Providers
In general, a component should be a moniker provider when it allows access to
one of its objects, while still controlling the object's storage. If a
component is going to hand out monikers that identify its objects, it must be capable
of performing the following tasks:
- On request, create a moniker that identifies an object.
- Enable the moniker to be bound when a client calls IMoniker::BindToObject on it.
A moniker provider must create a moniker of an appropriate
moniker class to identify an object. The moniker class refers to a specific implementation
of the
IMoniker interface that defines the type of moniker created. While you can create a
new moniker class through an implementation of the
IMoniker interface, it is frequently unnecessary because OLE provides five different
moniker classes, each with its own CLSID:
- File moniker
- Composite Moniker
- Item Moniker
- Anti-moniker
- Pointer moniker
The file, composite, and item monikers are the most frequently used monikers,
as they can be used to make nearly any object in any location. Anti- and
pointer monikers are primarily used inside OLE, but have some application in
implementing custom monikers.
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database
