MeexReay/racinfo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(protocol): write about recv messages in wrac

Browse Source
This commit is contained in:
MeexReay 2025-06-24 13:56:06 +03:00 committed by GitHub
parent 0875796999
commit dc2792aab9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
src/app/protocol/wrac/page.tsx
View File

@ -26,7 +26,25 @@ export default function Wrac() {
<Text>
WRAC (WebSocket Real Address Chat) is a community-made successor to
RAC that uses WebSockets instead of TCP. It uses the same requests as
RAC, but you should send data in binary format.
RAC, but you should send data in binary format. Also, you can use the
same connection multiple times, what differs from the usual RAC, where
you had to connect the server each time you made some request. That
causes some differences in the receiving messages.
</Text>
<Title id={"receiving-messages"}>Receiving messages</Title>
<Text>
As the connection now can be keep-alive, and the websocket uses messages
for transactions, we can't just do the same as we did in RAC to get the messages.
</Text>
<Text>
Now, to use those packets (<InlineCode>0x01</InlineCode> for normal reading and <InlineCode>0x02</InlineCode> for chunked reading),
we need to let the server know that we want to use them, and not send
messages (the same packet-ids). The way how to do this is just add the byte <InlineCode>0x00</InlineCode> to the start
of packets. For example: <InlineCode>0x00</InlineCode> <InlineCode>0x01</InlineCode> for normal reading.
</Text>
<Text>
This way we can separate the packets that receive data from the packet that receives the total size.
In this sense, WRAC solves a big problem with usual RAC.
</Text>
<Footer />
</main>