Unregistering routes

[danielepolencic]

Is it possible to unregister routes?

Example:

app.on('GET', '/temp', handler|middleware...)

after some time:

app.off('GET', '/temp')

The use case is: that we have actors that are spun and destroyed dynamically.

[revskill10]

I think you can "hack" by overriding with a noOpHandler ?

[CyanChanges]

But it's still there and what if you want to add a same or similar route?

[maou-shonen]

Why not use middleware?

[maou-shonen]

This can be completely customized based on your needs... for example, storing an App for each route or something like that...

[CyanChanges]

This can be completely customized based on your needs... for example, storing an App for each route or something like that...

So storing app for each cause memory leak(because you can't delete rout in root app), storing routes and recreate when change decrease the performance?

[CyanChanges]

Damn, looks like i am implementing a libc mallloc() my self

[maou-shonen]

This won't cause a memory leak. I don't understand why you're limiting the solution to the router.

[CyanChanges]

This won't cause a memory leak. I don't understand why you're limiting the solution to the router.

For example, a plugin(actor) registered on "/web"
And it created a new Hono app and register it on the root app
And then the plugin get removed, and what to do? replace the original app with a new do nothing app?
The do nothing app costs memory. And it would live forever. Because root Hono app have referred it.
What if the plugin load again, what if the plugin have a sub-plugin register on "/web/api"?
There will be a bunch of do nothing hono app costing memory.

[yusukebe]

How about using except in the Combine Middleware?
https://hono.dev/docs/middleware/builtin/combine#except