hero_voice_http: Consider /rpc/{context} for consistency with context-aware services #5

New issue

Open

opened 2026-02-24 12:00:42 +00:00 by mahmoud · 0 comments

mahmoud commented

2026-02-24 12:00:42 +00:00

Owner

Description

Currently hero_voice_http proxies RPC calls via POST /rpc (no context segment), which is correct since hero_voice is a global service with a single backend socket.

However, the hero_service spec §5 defines the HTTP proxy route as /rpc/{context} for all services. Context-aware services use the {context} segment to route to the right backend socket. Global services have no such routing need.

The question: Should global services also expose /rpc/{context} (with a fixed/ignored context, e.g. /rpc/global) for uniformity — so hero_proxy and SDK clients can use the same URL pattern for all services regardless of whether they are context-aware?

### Description Currently `hero_voice_http` proxies RPC calls via `POST /rpc` (no context segment), which is correct since hero_voice is a global service with a single backend socket. However, the hero_service spec §5 defines the HTTP proxy route as `/rpc/{context}` for all services. Context-aware services use the `{context}` segment to route to the right backend socket. Global services have no such routing need. The question: Should global services also expose /rpc/{context} (with a fixed/ignored context, e.g. /rpc/global) for uniformity — so hero_proxy and SDK clients can use the same URL pattern for all services regardless of whether they are context-aware?