Next steps

[delvedor]

Hi folks!
As discussed in #27 there are some things that we want to change, since all of those are breaking changes, let's discuss here how we plan to perform them and define how we will update the Upring architecture.

Points of discussion:

• Move from actual tentacoli based requests to node core http2 implementation
  • How we will support fire and forget request?
• Change the current routing model to a more user friendly one.
  • find-my-way could be an option but we should use the compatibility api. We can refactor it as upring-router in a way that supports just the http2 specifc api.
  • if we choose to use find-my-way we can even think about an encapsulation model like the one built in Fastify
• Introduce a tracing api
• Change the shape of the request object
  • Handle requests id
  • Add logging support

Feel free to update the above list with other points that we should discuss.

[IfnotFr]

I am using the stack of find-my-way + http2 instead of fastify for a backend file manager.

I may help on this if the project is till going.

Do you have some maintainers or time you will consume on this project on the future ?

[mcollina]

I don't think so :(.

[IfnotFr]

Oh, sad, anyway thanks for the reply ... i will find another way for solving my architecture problem ^^"