Export (0) Print
Expand All

4 Protocol Examples

To post his grocery list of celery and broccoli to a bulletin board, Joe creates a bulletin board post, adds a subject and body, and places it in a folder. The following is a description of what a client might do to accomplish Joe's intentions and the responses a server might return.

To create a Post object, the client sends a RopCreateMessageROP request ([MS-OXCROPS] section 2.2.6.2). The server returns a success code and a handle to a Message object.

After Joe has input his content for the Post object, the client transmits his data to the server by sending a RopSetProperties ROP request ([MS-OXCROPS] section 2.2.8.6).

Property

Property ID

Property type

Value

PidTagIconIndex (section 2.2.2.3)

0x1080

0x0003

(PtypInteger32 ([MS-OXCDATA] section 2.11.1))

0x00000001

PidTagMessageClass (section 2.2.2.4)

0x001A

0x001F

(PtypString ([MS-OXCDATA] section 2.11.1)

"IPM.Post"

PidTagNormalizedSubject ([MS-OXCMSG] section 2.2.1.10)

0x0E1D

0x001F

"Grocery List"

PidTagSubjectPrefix ([MS-OXCMSG] section 2.2.1.9)

0x003D

0x001F

""(null)

PidTagConversationTopic (section 2.2.2.2)

0x0070

0x001F

"Grocery List"

PidTagConversationIndex (section 2.2.2.1)

0x0071

0x0102

(PtypBinary [MS-OXCDATA] section 2.11.1)

(Set as described in note 1 following this table.)

PidTagHtml ([MS-OXCMSG] section 2.2.1.56.9)

0x1013

0x0102

<html>

<head>

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

</head>

<body lang=EN-US>

<p>Celery</p>

<p>Broccoli</p>

</body>

</html>

PidTagSenderName ([MS-OXOMSG] section 2.2.1.51)

0x0C1A

0x001F

"Joe Healy"

PidTagSenderAddressType ([MS-OXOMSG] section 2.2.1.48)

0x0C1E

0x001F

"EX"

PidTagSenderEntryId ([MS-OXOMSG] section 2.2.1.50)

0x0C19

0x0102

(Set as described in note 2 following this table.)

PidTagSenderSearchKey ([MS-OXOMSG] section 2.2.1.52)

0x0C1D

0x0102

(Set as described in note 3 following this table.)

PidTagSentRepresentingName ([MS-OXOMSG] section 2.2.1.57)

0x0042

0x001F

"Joe Healy"

PidTagSentRepresentingAddressType ([MS-OXOMSG] section 2.2.1.54)

0x0064

0x001F

"EX"

PidTagSentRepresentingEntryId ([MS-OXOMSG] section 2.2.1.56)

0x0041

0x0102

(Set as described in note 2 following this table.)

PidTagSentRepresentingSearchKey ([MS-OXOMSG] section 2.2.1.58)

0x003B

0x0102

(Set as described in note 3 following this table.)

Notes

  1. The PidTagConversationIndex property is set with a depth of 1 and has the following binary contents:

    0000: 01 C8 73 2D A1 0A 3E B3-EE 24 90 F4 45 BE 97 10
    0010: 90 B2 A5 07 7A 13
  2. The values of the PidTagSenderEntryId and PidTagSentRepresentingEntryId properties are identical because Joe isn't posting this on behalf of another user. These properties have the following 125-byte value:

    0000: 00 00 00 00 DC A7 40 C8-C0 42 10 1A B4 B9 08 00 ......@..B......
    0010: 2B 2F E1 82 01 00 00 00-00 00 00 00 2F 4F 3D 46 +/........../O=F
    0020: 49 52 53 54 20 4F 52 47-41 4E 49 5A 41 54 49 4F IRST ORGANIZATIO
    0030: 4E 2F 4F 55 3D 45 58 43-48 41 4E 47 45 20 41 44 N/OU=EXCHANGE AD
    0040: 4D 49 4E 49 53 54 52 41-54 49 56 45 20 47 52 4F MINISTRATIVE GRO
    0050: 55 50 20 28 46 59 44 49-42 4F 48 46 32 33 53 50 UP (FYDIBOHF23SP
    0060: 44 4C 54 29 2F 43 4E 3D-52 45 43 49 50 49 45 4E DLT)/CN=RECIPIEN
    0070: 54 53 2F 43 4E 3D 4A 48-45 41 4C 59 00          TS/CN=JHEALY.
  3. The values of PidTagSenderSearchKey and PidTagSentRepresentingSearchKey properties are identical because Joe isn't posting this on behalf of another user. The contents of these properties are used as Joe's search key. These properties have the following 100-byte value:

    0000: 45 58 3A 2F 4F 3D 46 49-52 53 54 20 4F 52 47 41 EX:/O=FIRST ORGA
    0010: 4E 49 5A 41 54 49 4F 4E-2F 4F 55 3D 45 58 43 48 NIZATION/OU=EXCH
    0020: 41 4E 47 45 20 41 44 4D-49 4E 49 53 54 52 41 54 ANGE ADMINISTRAT
    0030: 49 56 45 20 47 52 4F 55-50 20 28 46 59 44 49 42 IVE GROUP (FYDIB
    0040: 4F 48 46 32 33 53 50 44-4C 54 29 2F 43 4E 3D 52 OHF23SPDLT)/CN=R
    0050: 45 43 49 50 49 45 4E 54-53 2F 43 4E 3D 4A 48 45 ECIPIENTS/CN=JHE
    0060: 41 4C 59 00                                     ALY.

When Joe is ready to save his changes, the client commits the properties on the server by sending a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 2.2.6.3) and then releases the handle for the Message object by sending a RopRelease ROP request ([MS-OXCROPS] section 2.2.15.3).

The values of some properties will change during the processing of the RopSaveChangesMessageROP, but the properties specified in section 2.2.2 will not change.

Show:
© 2015 Microsoft