|
IRunningObjectTable
The IRunningObjectTable interface manages access to the Running Object Table (ROT), a globally
accessible lookup table on each workstation. A workstation's ROT keeps track of those
objects that can be identified by a moniker and that are currently running on
the workstation. When a client tries to bind a moniker to an object, the
moniker checks the ROT to see if the object is already running; this allows the
moniker to bind to the current instance instead of loading a new one.
The ROT contains entries of the form:
(pmkObjectName, pUnkObject)
The pmkObjectName element is a pointer to the moniker that identifies the running object. The pUnkObject element is a pointer to the running object itself. During the binding
process, monikers consult the pmkObjectName entries in the Running Object Table to see if an object is already running.
Objects that can be named by monikers must be registered with the ROT when
they are loaded and their registration must be revoked when they are no longer
running.
When to Implement
You do not need to implement this interface. The system provides an
implementation of the Running Object Table that is suitable for all situations.
When to Use
You typically use the ROT if you're a moniker provider (that is, you hand out
monikers identifying your objects to make them accessible to others) or if
you're writing your own moniker class (that is, implementing the IMoniker interface).
If you are a moniker provider, you register your objects with the ROT when
they begin running and revoke their registrations when they are no longer running.
This enables the monikers that you hand out to be bound to running objects.
You should also use the ROT to record the object's last modification time. You
can get an IRunningObjectTable interface pointer to the local ROT by calling the GetRunningObjectTable API function.
The most common type of moniker provider is a compound-document link source.
This includes server applications that support linking to their documents (or
portions of a document) and container applications that support linking to
embeddings within their documents. Server applications that do not support linking
can also use the ROT to cooperate with container applications that support
linking to embeddings.
If you are writing your own moniker class, you use the ROT to determine
whether a object is running and to retrieve the object's last modification time. You
can get an IRunningObjectTable interface pointer to the local ROT by calling the IBindCtx::GetRunningObjectTable method on the bind context for the current binding operation. Moniker
implementations should always use the bind context to acquire a pointer to the ROT;
this allows future implementations of IBindCtx to modify binding behavior. Note that you must also implement the IROTData interface on your moniker class in order to allow your monikers to be
registered with the ROT.
Methods in VTable Order
IRunningObjectTable Methods
| Description
| Register
| Registers an object with the ROT.
| Revoke
| Revokes an object's registration with the ROT.
| IsRunning
| Checks whether an object is running.
| GetObject
| Returns a pointer to an object given its moniker.
| NoteChangeTime
| Notifies the ROT that an object has changed.
| GetTimeOfLastChange
| Returns the time an object was last changed.
| EnumRunning
| Returns an enumerator for the ROT.
|
See Also
IBindCtx::GetRunningObjectTable, IROTData, GetRunningObjectTable
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|