From 3843c98d95d956d391233fc2dab02a57b3015801 Mon Sep 17 00:00:00 2001 From: Jakio815 <74869052+Jakio815@users.noreply.github.com> Date: Tue, 27 Feb 2024 18:27:25 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=20ec3b6?= =?UTF-8?q?de42a8671e8009682cdfe33343b4a436de1=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- d9/da6/net__common_8h.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/d9/da6/net__common_8h.html b/d9/da6/net__common_8h.html index 067ccaaf8..e380d88f9 100644 --- a/d9/da6/net__common_8h.html +++ b/d9/da6/net__common_8h.html @@ -1001,7 +1001,7 @@

-

Byte identifying a timestamped message to forward to another federate. The next two bytes will be the ID of the destination reactor port. The next two bytes are the destination federate ID. The four bytes after that will be the length of the message. The next eight bytes will be the timestamp of the message. The next four bytes will be the microstep of the message. The remaining bytes are the message.

+

Byte identifying a timestamped message to forward to another federate. The next two bytes will be the ID of the destination reactor port. The next two bytes are the destination federate ID. The four bytes after that will be the length of the message (as an unsigned 32-bit int). The next eight bytes will be the timestamp of the message. The next four bytes will be the microstep of the message. The remaining bytes are the message.

With centralized coordination, all such messages flow through the RTI. With decentralized coordination, tagged messages are sent peer-to-peer between federates and are marked with MSG_TYPE_P2P_TAGGED_MESSAGE.