4.3 Flooding a Message

A sample flood message follows.

 (00)<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
                 xmlns:wsa10="http://www.w3.org/2005/08/addressing">
 (01) <s:Header>
 (02) <wsa10:Action s:mustUnderstand="1">http://MyPeerApplication/MyMethod<
 /wsa10:Action>
 (03) <wsa10:To s:mustUnderstand="1">net.p2p:// MyPeerApplication/</wsa10:To>
 (04) <MessageID xmlns="http://schemas.microsoft.com/net/2006/05/peer">
 urn:uuid:271dddd4-fa44-46e2-9b86-090c0a52326c</MessageID>
 (05) <PeerTo xmlns="http://schemas.microsoft.com/net/2006/05/peer">net
 .p2p://ApplicationMeshName/Channel1/</PeerTo>
 (06)   <PeerVia xmlns="http://schemas.microsoft.com/net/2006/05/peer">
 net.p2p://ApplicationMeshName/Channel1</PeerVia>
 (07)    <FloodMessage xmlns="http://schemas.microsoft.com/net/2006/05/
 peer">PeerFlooder</FloodMessage>
 (08)   </s:Header>
 (09)  <s:Body>
 (10)  </s:Body>
 (11)</s:Envelope>

Other than the following Peer Channel Protocol–specific header (that a node adds to the message; see section 3.2), this message is the same as the application message.

04 - Demonstrates a MessageID header containing a serialized GUID as its element text.

05 - Demonstrates a PeerTo header containing the application target endpoint. On a received message, this header is used to route the message to the appropriate message processing endpoint. It contains the URI of the endpoint that ultimately processes the message.

06 - Demonstrates the PeerVia header containing the URI of the channel type that is sending the message. PeerVia and PeerTo are the same.

07 - Demonstrates the FloodMessage header. This header is always present with "PeerFlooder" as the single text node value, if the message is to be treated as a flood message by the node.