chanx-go

Handlers, not a switch

Each action gets a typed method: HandleChat(ctx, ChatMessage). No json.RawMessage, no switch on msg.Type.

Validated before your code runs

Payloads are checked against a JSON Schema inferred from the struct. A bad frame gets an error frame in Pydantic's format; your handler never sees it.

Groups and topics across processes

Broadcast to rooms, push from HTTP handlers and workers, let clients subscribe to many streams over one socket. Over Redis, every process is reached.

AsyncAPI from the code

The document is built from the handlers that serve traffic, so it cannot drift. Typed clients for Go, TypeScript and Python are generated from it.

Your framework

net/http, chi, gorilla/mux, gin, echo and Fiber. Routes live in your router and your middleware runs before the upgrade.

One protocol with Python and Node

Same frames, same AsyncAPI, same Redis layer as chanx and chanx-js: their clients work unchanged, and Go and Python processes share groups.

A consumer in Go

type ChatConsumer struct{}

// Groups puts each connection in its room, from the {room} path parameter.
func (ChatConsumer) Groups(c *chanx.Conn) []string { return []string{"room." + c.Param("room")} }

// Emits declares what the consumer sends besides replies.
func (ChatConsumer) Emits() []chanx.Message { return []chanx.Message{ChatNotification{}} }

func (ChatConsumer) HandleChat(ctx *chanx.Context, m ChatMessage) error {
	return ctx.Broadcast(ChatNotification{Payload: m.Payload})
}

func (ChatConsumer) HandlePing(ctx *chanx.Context, _ chanx.PingMessage) (chanx.PongMessage, error) {
	return chanx.PongMessage{}, nil
}

Mount it, and two clients in /ws/chat/lobby talk:

json

> {"action": "chat", "payload": {"text": "hi"}}
< {"action": "chat_notification", "payload": {"text": "hi"}}

A frame that does not match the message never reaches HandleChat: