hero_voice_http: Consider /rpc/{context} for consistency with context-aware services #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Currently
hero_voice_httpproxies RPC calls viaPOST /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?