pondsocket-axum 0.1.2

Axum WebSocket adapter for PondSocket.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

# PondSocket Rust

Rust implementation of PondSocket with the same wire protocol as the JavaScript,
Go, and Python implementations.

## Crates

| Crate | Purpose |
|---|---|
| `pondsocket-common` | Shared wire enums, schemas, message parsing, UUID helper |
| `pondsocket` | Core server model: endpoints, lobbies, channels, contexts, presence, pubsub |
| `pondsocket-axum` | Axum WebSocket adapter |

## Features

- Endpoint connection authorization.
- Channel pattern matching with `:param`, `prefix:param`, wildcard, and query support.
- Join, leave, broadcast, reply, system events, and presence events.
- Server-side assigns.
- Outgoing message handlers that can transform or block delivery.
- Local in-memory pubsub.
- Optional Redis pubsub with `pondsocket/redis`.
- Cross-node broadcast delivery, targeted broadcast recipient metadata, assigns updates, and user eviction commands.

## Development

```bash
cargo test
cargo test -p pondsocket --features redis
```

## Wire Shape

Inbound client messages use the existing camelCase protocol:

```json
{
  "action": "BROADCAST",
  "event": "message",
  "channelName": "/chat/1",
  "requestId": "request-id",
  "payload": {}
}
```

Presence messages keep the JS/Python payload shape:

```json
{
  "action": "PRESENCE",
  "event": "JOIN",
  "channelName": "/chat/1",
  "requestId": "request-id",
  "payload": {
    "presence": [],
    "changed": {}
  }
}
```