Here are some best practices for configuring Sandstar Web Socket connections in production:
-
Use a dedicated WebSocket port - Keep the WebSocket server on its own port (default 7070) separate from your SkySpark HTTP traffic.
-
Monitor session pool usage - Each Sedona device supports a maximum of 2 concurrent SOX sessions. Use the
/live/soxstatusendpoint to monitor active connections. -
Set appropriate timeouts - The default 5-minute idle timeout works for most use cases. For dashboards that poll less frequently, consider increasing it.
-
Plan for reconnection - The WebSocket server handles automatic reconnection with exponential backoff. Your client code should listen for connection state changes.
Great overview. One thing to add: the session pool limit of 2 per device is a Sedona hardware constraint, not a software one. Plan your architecture accordingly.
Log in to reply.