ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Vaadin Flow's @Push lets the server update the UI instantly, but silent transport fallbacks and CSP rules can break it. Here is how to enable it safely and verify the connection.
NGINX’s HTTP/2 server push can reduce page load time by sending critical assets before the browser asks. This guide shows how to enable, verify, and weigh the trade‑offs of server push in a production environment.
The goal is to enable nginx’s http2_push_preload feature to preload critical assets via the X-Accel-Redirect header while keeping alert noise low by suppressing unnecessary push‑related warnings. Because the directive is marked experimental, its behavior may change across versions, it interacts with caching layers (potentially causing duplicate pushes when a
Goal Clarify the appropriate default PushMode for Vaadin 24 applications. Context Vaadin 24 introduced Server Push via WebSocket, yet the framework’s default remains PushMode.MANUAL . The documentation acknowledges both modes but does not recommend a default for all applications, leaving the decision to developers. Uncertainty For many CRUD‑style application
Vaadin Flow keeps UI component state server-side per user session and serializes access with a session lock, so concurrent requests from the same browser are queued rather than processed in parallel. Server push is opt-in per UI and the transport mode is configurable, with documented fallback to long polling when WebSocket is unavailable. Behavior depends on
vaadin
nginx