Partager via


2.2 Message Syntax

Browser messages are transported via the Mailslot Protocol, as specified in section 2.1. The browser message MUST be contained in the data section of the Mailslot message.

Browser messages can be categorized according to the server's role. Each of these lists is complete for the specified, individual role. A machine that assumes multiple roles will use the messages for each of those roles, as described here:

More information about how the various browser server messages are used is specified in section 3.

All multibyte fields specified in messages in this section are transmitted in little-endian byte order, unless noted otherwise.

Browser message opcodes

A browser message operation code (opcode) consists of an 8-bit numeric value. The opcode MUST be one of the values listed in the following table.

Value

Meaning

HostAnnouncement

0x01

For more information, see section 2.2.1.

AnnouncementRequest

0x02

For more information, see section 2.2.2.

RequestElection

0x08

For more information, see section 2.2.3.

GetBackupListRequest

0x09

For more information, see section 2.2.4.

GetBackupListResponse

0x0A

For more information, see section 2.2.5.

BecomeBackup

0x0B

For more information, see section 2.2.6.

DomainAnnouncement

0x0C

For more information, see section 2.2.7.

MasterAnnouncement

0x0D

For more information, see section 2.2.8.

ResetStateRequest

0x0E

For more information, see section 2.2.9.

LocalMasterAnnouncement

0x0F

For more information, see section 2.2.10.