dynamic websocket routes about fastify-websocket HOT 3 CLOSED

dynamically defining routes is likely to lead to memory leaks, and therefore is not supported.

from fastify-websocket.

Fastify works best if you define all your routes up front which you can do using parameters in the route template, like

fastify.get(`/ws/:userID`, { websocket: true }, () => {})

If you declare that route once at the top level then all requests with that pattern will hit that route handler. If you need to authenticate that route, you can use normal session plugins like fastify-secure-session and a preValidate handler, or you could use something like JWT tokens that you pass to the user like you are doing with the listen key. Creating new routes at runtime is gonna be slow and suck up a lot of memory and so it is unsupported in fastify, see fastify/fastify#1771.

from fastify-websocket.

Fastify works best if you define all your routes up front which you can do using parameters in the route template, like

fastify.get(`/ws/:userID`, { websocket: true }, () => {})

If you declare that route once at the top level then all requests with that pattern will hit that route handler. If you need to authenticate that route, you can use normal session plugins like fastify-secure-session and a preValidate handler, or you could use something like JWT tokens that you pass to the user like you are doing with the listen key. Creating new routes at runtime is gonna be slow and suck up a lot of memory and so it is unsupported in fastify, see fastify/fastify#1771.

thanks! thats what i was looking for.

from fastify-websocket.