ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Allow applications to tune the exponential backoff schedule used when a Turbo Streams connection drops, so that reconnection aggressiveness can match infrastructure constraints such as load-balancer idle timeouts or upstream rate limits. Constraints and uncertainty Turbo 8.x implements a built-in reconnection loop with a starting delay near 500 ms and a
Angular Proxy vs Spring Boot CORS In JHipster‑generated projects the Angular proxy (proxy.conf.json) forwards API calls to the Spring Boot backend during development. The backend typically registers a CORS filter that controls cross‑origin request handling. When both the proxy and filter are active, the forwarding of cookies and authorization headers is unce
After a Feathers websocket handshake completes, the authentication plugin populates params.user and params.authenticated for subsequent service calls without re-validating the JWT on every message. Because the token is not re-checked per event, an expired or revoked JWT does not automatically disconnect the client; the socket remains in channels and continue
A Socket.IO 4.x server on Node.js, paired with the official JavaScript client, must be sized for a workload where latency is expected to surface only when concurrent connections and emits ramp up. The open decision is where such latency would belong: the Engine.IO polling-to-WebSocket upgrade path, the single process's event loop, or the multi-node adapter l
Goal Determine whether a Turbo Streams WebSocket connection remains open or automatically reconnects when the server detects that a user’s authentication has expired or been revoked. Constraints Least‑privilege enforcement relies on server‑side middleware; the stream endpoint must reject messages from unauthenticated or unauthorized users. When a session tok
WebSocket connection behavior in collection runs Hoppscotch supports executing multiple WebSocket requests as part of a collection run. Each request can target the same endpoint, yet the documentation does not clarify whether the client reuses an existing WebSocket connection or opens a new one for each request in the sequence. Browser developer tools show a
The goal is to select a backpressure exposure strategy for an Akka Streams pipeline that emits high‑frequency events to a WebSocket sink serving a UI client, while keeping the UI responsive and avoiding client‑side overload. Constraints include the need for the client to honor the chosen flow‑control mechanism, the trade‑off between latency introduced by bac
Goal Determine whether the ignoreHTTPSErrors:true launch option in Puppeteer also suppresses SSL certificate errors for WebSocket connections initiated from a page. Current Constraints Chromium’s ignoreHTTPSErrors flag is documented to affect navigation, XHR, and fetch, but its coverage of WebSocket handshakes remains unverified. Puppeteer exposes the flag v
Goal Determine whether ngrok’s handling of WebSocket upgrades is the source of frame loss or latency spikes when the local development server receives more than 200 concurrent connections. Constraints & Uncertainty ngrok 3.x injects a TLS termination layer adding 5–15 ms per request. Its core runs a single‑threaded event loop, which may become a CPU bott
turbo
jhipster
feathersjs
nodejs
socketio
hoppscotch
akka
puppeteer
ngrok