Skip to content

Commit f1878d2

Browse files
committed
#65 fix typo
1 parent caf4f9f commit f1878d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

v2-0-RC1/doc/03MessageStructure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Message Structure
44
Message Framing
55
------------------------------------------------------------------------------------------------------------------------------------------------------------
66

7-
SBE messages have no defined message delimiter. Version 2.0 of SBE makes it possible to walk the elements of a message to determine its limit, even when the message has been extended. Nevertheless, since internal framing depends on a correct starting point and not encountering malformed messages, it may be desirable to use an external framing protocol when used with transports that do not preserve message boundaries, such as when they are transmitted on a streaming
7+
SBE messages have no defined message delimiter. SBE makes it possible to walk the elements of a message to determine its limit, even when the message has been extended. Nevertheless, since internal framing depends on a correct starting point and not encountering malformed messages, it may be desirable to use an external framing protocol when used with transports that do not preserve message boundaries, such as when they are transmitted on a streaming
88
session protocol or when persisting messages in storage.
99

1010
### Simple Open Framing Header
@@ -250,7 +250,7 @@ Example of fields with specified offsets
250250
| Symbol | 8 | 0 | 20 |
251251

252252
#### Field byte alignment
253-
As an alternative to specifying a field's offset from the start of a block, its byte alignment may be specified. If specified, the start of the a field should reside at an offset from the start of the buffer that is the next multiple of the alignment attribute. If the offset without alignment would not be a multiple of the alignment attribute, then the buffer is padded with octets to that multiple. The padding should be set to binary zeroes.
253+
As an alternative to specifying a field's offset from the start of a block, its byte alignment may be specified. If specified, the start of a field should reside at an offset from the start of the buffer that is the next multiple of the alignment attribute. If the offset without alignment would not be a multiple of the alignment attribute, then the buffer is padded with octets to that multiple. The padding should be set to binary zeroes.
254254

255255
The alignment attribute is mutually exclusive with offset.
256256

0 commit comments

Comments
 (0)