Story: NATS service discovery for HTTP base URL
Table of Contents
This page documents a story in Sprint 15. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Qt client automatically discovers the HTTP server's base URL via NATS so users don't need to configure http_port manually.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 15 |
| Now | Completed 2026-03-22. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-03-22 |
Acceptance
- Auto-discovery of HTTP base URL post-login.
- Protocol types in ores.http shared utility lib (ores.qt no longer links ores.http.server).
- Architecture migration plan for *.api / *.core split.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Add NATS service discovery for HTTP base URL | DONE | 2026-05-20 | 2026-03-22 | Qt client automatically discovers the HTTP server's base URL after login via NATS; protocol types moved to ores.http shared utility lib so ores.qt can include them without linking ores.http.server; architecture migration plan added for splitting service libraries into *.types + *.core (later refined to *.api + *.core). |
Decisions
- NATS-based discovery
- same channel as the rest of the comms; no need for a separate discovery mechanism.
Out of scope
- Multi-instance HTTP failover (future).
See also
- API/core architecture migration — the architectural split this story plans + the next stories implement.