2018-04-13 03:18:42 +02:00
|
|
|
# Websocket chat example
|
|
|
|
|
2022-03-08 16:49:32 +01:00
|
|
|
This is extension of the [actix chat example](https://github.com/actix/examples/tree/HEAD/websockets/chat)
|
2018-04-13 03:18:42 +02:00
|
|
|
|
|
|
|
Added features:
|
|
|
|
|
2022-03-06 01:43:10 +01:00
|
|
|
- Browser WebSocket client
|
|
|
|
- Chat server runs in separate thread
|
|
|
|
- Tcp listener runs in separate thread
|
|
|
|
- Application state is shared with the websocket server and a resource at `/count/`
|
2018-04-13 03:18:42 +02:00
|
|
|
|
|
|
|
## Server
|
|
|
|
|
2020-11-30 13:41:33 +01:00
|
|
|
1. Chat server listens for incoming tcp connections. Server can access several types of message:
|
2018-04-13 03:18:42 +02:00
|
|
|
|
2022-03-06 01:43:10 +01:00
|
|
|
- `/list` - list all available rooms
|
|
|
|
- `/join name` - join room, if room does not exist, create new one
|
|
|
|
- `/name name` - set session name
|
|
|
|
- `some message` - just string, send message to all peers in same room
|
|
|
|
- client has to send heartbeat `Ping` messages, if server does not receive a heartbeat message for 10 seconds connection gets dropped
|
2018-04-13 03:18:42 +02:00
|
|
|
|
2022-03-06 01:43:10 +01:00
|
|
|
2. [http://localhost:8080/count/](http://localhost:8080/count/) is a non-websocket endpoint and will affect and display state.
|
2020-11-30 13:41:33 +01:00
|
|
|
|
2018-09-24 10:57:36 +02:00
|
|
|
To start server use command: `cargo run --bin websocket-chat-server`
|
2018-04-13 03:18:42 +02:00
|
|
|
|
|
|
|
## Client
|
|
|
|
|
|
|
|
Client connects to server. Reads input from stdin and sends to server.
|
|
|
|
|
2018-09-24 10:57:36 +02:00
|
|
|
To run client use command: `cargo run --bin websocket-chat-client`
|
2018-04-13 03:18:42 +02:00
|
|
|
|
|
|
|
## WebSocket Browser Client
|
|
|
|
|
|
|
|
Open url: [http://localhost:8080/](http://localhost:8080/)
|