Skip to content

Commit 0b98fad

Browse files
committed
Fix broken links
1 parent 0422e54 commit 0b98fad

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_posts/2018-06-29-using-stompjs-v5.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -201,14 +201,14 @@ web_stomp.ws_frame = binary
201201

202202
### Publishing binary messages
203203

204-
Use parameter `binaryBody` of [Client#publish](/api-docs/latest/classes/Client.html#publish) to send binary data of type [Uint8Array].
204+
Use parameter `binaryBody` of [Client#publish](/api-docs/latest/classes/Client.html#publish) to send binary data of a type [Uint8Array].
205205

206206
See [Send messages](#send-messages) for an example.
207207

208208
### Receiving binary messages
209209

210-
The library does not guess whether the incoming data is text/binary.
211-
To access the message body as a string, please use [Message#body](/api-docs/latest/interfaces/IFrame.html#body) and to access it as binary, please use [Message#binaryBody](/api-docs/latest/classes/Frame.html#binaryBody).
210+
The library does not guess whether the incoming datum is text/binary.
211+
To access the message body as a string, please use [Message#body](/api-docs/latest/interfaces/IFrame.html#body) and to access it as binary, please use [Message#binaryBody](/api-docs/latest/interfaces/IFrame.html#binaryBody).
212212

213213
There is no generally accepted convention in STOMP (actually messaging in general) to indicate binary messages. Therefore, the message senders and receivers must agree on the required convention. For example, you may choose to set a `content-type` header to indicate a binary message.
214214

0 commit comments

Comments
 (0)