Skip to main content

One doc tagged with "websocket"

View all tags

Native HTTP on the process port

By default, Genesis processes exchange messages with each other over raw TCP, and only GENESIS_ROUTER answers HTTP requests. If you switch a process to the WebSocket messaging channel, it keeps serving Genesis messaging and also answers plain HTTP on the same port, the process's port from its service definition (*-service-definitions.xml). Under Genesis Start with a port offset, the port is shifted; the Application view shows the port each process was given. Each of its request servers, event handlers and custom endpoints gets an HTTP route. You can call those routes directly from inside your cluster, or let the Genesis Router forward HTTP requests to them as a proxy.