Called by the client of a class object to keep an open object application in
memory, allowing instances to be created more quickly.
| BOOL fLock
||//Increments or decrements the lock count
, increments the lock count; if FALSE
, decrements the lock count.
The specified object was either locked ( fLock
= TRUE) or unlocked from memory ( fLock
Indicates an unspecified error.
Out of memory.
An unexpected error occurred.
IClassFactory::LockServer controls whether an object application is kept in memory. Keeping the
application alive in memory allows instances to be created more quickly.
Notes to Callers
Most clients do not need to call this function. It is provided only for the
benefit of sophisticated clients that require special performance in the creation
of certain kinds of objects.
Notes to Implementors
If the lock count is zero, there are no more objects in use, and the
application is not under user control, then the server can be closed. One way to
is to call CoLockObjectExternal
The process that locks the object application is responsible for unlocking it.
Once the class object is released, there is no mechanism that guarantees the
caller connection to the same object definition later (as in the case where a
class object is registered as single-use). It is important to count all calls,
not just the last one, to IClassFactory::LockServer
, because calls must be balanced before attempting to release the pointer to
the class object or an error results. For every call to LockServer
set to TRUE, there must be a call to LockServer
set to FALSE. When the lock count and the class object reference count are
both zero, the class object can be freed.
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages