Savory/Danet

HTTP engine abstraction

Sorikairox opened this issue · 6 comments

For now, DanetApplication references an oak Application. We should abstract it to prepare for other HTTP engines

According this bench oak is not so performant -> https://github.com/denosaurs/bench
It's like express in node world:)
Waiting for http abstraction...

Hi, I'd like to take care of this issue

Sure

@Sorikairox cheetah will hit v1.0 on July 7 and I'd like to partner up with you, so people can choose between these two.

Deno.serve is stable and would be a good alternative.

We moved from Oak to Hono in V2. Not planning to handle multiple engine for now, closing this issue.