OBJREF is the name of the structure of marshalled interfaces in COM and DCOM. Because COM interfaces can only be called directly from the context (like a thread, process or machine) where they originated, when they are needed in another context they are marshalled in this structure, which is then passed to the destination context where it is unmarshalled to a proxy that takes care of the necessary communication, for example passing messages or network packets or marshalling other interfaces passed in calls.[1][2]
Format
The layout of the structure is as follows:[3][4]
| Offset | Size | Description |
|---|---|---|
| 0 | 4 | Signature: 'MEOW' |
| 4 | 4 | Flag indicating the kind of structure |
| 8 | 16 | Interface identifier |
| Flag = 1: standard | ||
| 24 | 4 | Flags, mostly reserved for the system, but can be used to turn off pinging objects.[5] |
| 28 | 4 | Reference count |
| 32 | 8 | OXID – object exporter identifier[6] |
| 40 | 8 | OID – object identifier[6] |
| 48 | 16 | IPID – interface pointer identifier[7] |
| 64 | variable | DUALSTRINGARRAY |
| Flag = 2: handler (an extension of standard)[8] | ||
| 64 | 16 | Class identifier of a class that will be used as a handler for the interface, i.e. sit between the client and the proxy. |
| 80 | variable | DUALSTRINGARRAY |
| Flag = 4: custom marshalling[9] | ||
| 24 | 16 | Class identifier of the custom proxy |
| 40 | 4 | 0 (reserved value) |
| 44 | 4 | Size of the data below |
| 48 | variable | Custom marshalling data |
| Flag = 8: extended (also an extension of standard)[10] | ||
| 64 | 4 | Signature 'VYSN' |
| 68 | variable | DUALSTRINGARRAY |
| 4 | 1 (historically the number of data elements below, but there always is only a single element) | |
| 4 | Signature 'VYSN' | |
| Data element used to identify and marshal an envoy context:[11][12][13] | ||
| 16 | Context identifier[14] | |
| 4 | Size of the data below, excluding padding | |
| 4 | Size of the data below, including padding | |
| 8n | A marshalled envoy context, padded to a multiple of eight bytes | |
The layout of DUALSTRINGARRAY is:[15][16]
| Offset | Size | Description |
|---|---|---|
| 0 | 2 | Total number of entries in the arrays below, including nulls |
| 2 | 2 | Number of entries in the array that represent string bindings |
| 4 | 2n | String and security bindings |
The string bindings are null-terminated records specifying connection information, like IP addresses, and the security bindings are null-terminated records specifying authentication information. Both arrays are null-terminated too.
References
- ↑ Tim Ewald (2001-03-06). "The Mechanics of COM+". Informit. Pearson Education & Addison-Wesley Professional. Retrieved 2008-09-07.
- ↑ Mike Hearn (2005-01-22). "More DCOM notes". Wine Developer's List. Codeweavers. Retrieved 2008-09-07.
- ↑ "dcom.idl". Wine. CodeWeavers. 2003. Retrieved 2008-09-06.
- ↑ Dharma Shukla (1998). "ShowMeMyOBJREF". Retrieved 2008-09-07. (This is example code to inspect the contents of an OBJREF.)
- ↑ Eddon, Guy; Eddon, Henry (March 1998). "Understanding the DCOM Wire Protocol by Analyzing Network Data Packets". Microsoft Systems Journal. Microsoft. Retrieved 2008-09-07.
- 1 2 "Windows Protocols Master Glossary: O". MSDN. Microsoft. Retrieved 2008-09-06.
object exporter identifier (OXID): A 64-bit number that uniquely identifies an object exporter within an object server. … object identifier (OID): (1) In the context of an object server, a 64-bit number that uniquely identifies an object.
- ↑ "Windows Protocols Master Glossary: I". MSDN. Microsoft. Retrieved 2008-09-06.
interface pointer identifier (IPID): A 128-bit number that uniquely identifies an interface on an object within an object exporter.
- ↑ "OBJREF_HANDLER". MSDN. Microsoft. Retrieved 2008-09-06.
- ↑ "OBJREF_CUSTOM". MSDN. Microsoft. Retrieved 2008-09-07.
- ↑ "OBJREF_EXTENDED". MSDN. Microsoft. Retrieved 2008-09-06.
- ↑ "Context Properties". MSDN. Microsoft. Retrieved 2008-09-07.
- ↑ "Context Properties and Marshaling". MSDN. Microsoft. Retrieved 2008-09-07.
- ↑ "Windows Protocols Master Glossary: E". MSDN. Microsoft. Retrieved 2008-09-07.
envoy context: A context that is marshaled and returned to a client as a result of obtaining an object reference.
- ↑ "Windows Protocols Master Glossary: C". MSDN. Microsoft. Retrieved 2008-09-07.
context: A collection of context properties that describe an execution environment. sqq.
- ↑ "DUALSTRINGARRAY". MSDN. Microsoft. Retrieved 2008-09-06.
- ↑ Eddon, Guy; Eddon, Henry (1999). "Marshaled Interface Pointers". In Stroo, Eric; Turner, Alice; Young, Marc; Chang, Ina (eds.). Inside COM+ Base Services. Redmond: Microsoft Press. ISBN 0-7356-0728-1.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.