developers:websocket

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
developers:websocket [2025/03/14 19:06] – external edit 127.0.0.1developers:websocket [2025/03/14 19:15] (current) – [Message Structure Overview] chad
Line 27: Line 27:
  
 All messages sent to the server must be wrapped in a **ClientMessage** envelope, and all messages received from the server will be contained within a **ServerMessage** envelope. This ensures a consistent structure and simplifies message parsing. All messages sent to the server must be wrapped in a **ClientMessage** envelope, and all messages received from the server will be contained within a **ServerMessage** envelope. This ensures a consistent structure and simplifies message parsing.
- 
-A C# helper tool is available to streamline message handling. It is part of a repository that provides free utilities for developers. **[Repository Placeholder - Add Link]** 
  
 === Client Message Structure === === Client Message Structure ===
Line 64: Line 62:
 </code> </code>
  
-Each message type within these envelopes is Protobuf message, allowing for efficient serialization and deserializationDevelopers should extract the relevant fields based on their needs.+ 
 +=== Message Tools === 
 + 
 +The [[https://github.com/CTS-Futures/t4-api-tools|T4 API Tools repository]] has code that makes wrapping messages from your client very easy. 
 + 
 +<bootnote> 
 +Reach out to support if you would like API tool'for a language we have not covered yet. 
 +</bootnote> 
 + 
 +^ **Platform** ^ **Client Message Helper** ^ 
 +| **.Net** | [[https://github.com/CTS-Futures/t4-api-tools|ClientMessageHelper.cs]]| 
 + 
 + 
 + 
 + 
  
  • developers/websocket.1741979217.txt.gz
  • Last modified: 2025/03/14 19:06
  • by 127.0.0.1