M. Efe Çetin

> @efectn we could also use this for the ctx interface Sounds good idea

Sorry i didn't see it. You can create a PR @JonasDoe @tmarwen

Sounds good idea. Most part of our docs can be generated automatically.

> I think maybe we can support the websocket proxy and what do you think? @ReneWerner87 @efectn Agree

> I can check this out! I'll be making sure that the method can be thread-safe and make a PR You can check https://github.com/gofiber/fiber/tree/export-buildtree branch. I've implemented the necessary mutexes...

> @efectn To avoid the Mutex we would need a separate Tree that's a copy of the main one. We can then sync changes to that one if the User...

> @efectn @gaby I don't know if either of you are doing some work into this, but I've added a RebuildTree method with an extensive comment explaining all the reasons...

I'm OK with this change but it's breaking-change for v2. We should do it for v3. Can you change target to v3-beta @li-jin-gou

> @gofiber/maintainers what do we do with this solution, do we want to pursue it further? for this we would have to adapt the storage interface We can add new...

Hi. Can you provide a proof-of-concept? If we can do it without breaking something on v2, it's OK to me. Otherwise, we have to adjust logger middleware on v3.