But if you can’t keep a connection for too long and the whole point of streaming responses is to allow for responses that take too long, what’s even the point?
If server sent events are supported now thanks to fliud compute, my understanding is that websockets are too? But I don’t see that explicitly said anywhere. In fact, if anything, I see the opposite:
WebSockets are still not supported on Vercel, even with Fluid Compute enabled. The key distinction is streaming responses (which work great with Fluid Compute) are not the same as WebSocket connections (which require persistent, bidirectional connections that serverless functions can’t maintain).
What Fluid Compute enables:
Longer execution times for functions
Better support for server-sent events and streaming responses
Improved performance for long-running operations
What it doesn’t change:
WebSocket connections are still not supported
The serverless architecture still doesn’t allow persistent connections
But you can still have realtime features with your Vercel project by using one of the external providers listed in that first guide you linked
