Client-server communication #4

Open
opened 2025-09-09 20:11:47 +05:00 by pztrn · 0 comments
Owner

Client-server communication should:

  1. Use HTTP as basic transport - server should not implement own low-level protocols for communication.
  2. Use websockets for real-time communication - HTTP itself is a stateless protocol, but client connection will eventually need it's own state for realtimeness.
  3. Use JSON as real-time data format.
  4. Use separate HTTP requests for file loading - binary data should not come via websockets.
Client-server communication should: 1. **Use HTTP as basic transport** - server should not implement own low-level protocols for communication. 2. **Use websockets for real-time communication** - HTTP itself is a stateless protocol, but client connection will eventually need it's own state for realtimeness. 3. **Use JSON as real-time data format**. 4. **Use separate HTTP requests for file loading** - binary data should not come via websockets.
pztrn added this to the 0.1.0 milestone 2025-09-09 20:11:47 +05:00
pztrn added the
Kind
Feature
label 2025-09-09 20:11:47 +05:00
Sign in to join this conversation.
No description provided.