I'm looking for transport agnostic HTTP server implementation, similar to how Tungstenite works. That is:
- no async/await
- support for non-blocking usage (ie. can be "asyncified" externally)
- generic over Read+Write like Tungstenite (or some similar concept, specific trait doesn't matter)
Basically I'm looking for a something to replicate
tungstenite combo, but for HTTP.
Most frameworks I found are either async and based on some runtime like Tokio, or they impose thread per request execution model - I need something that doesn't do either and let the user handle that.
So far I've only found
rotor, which seems close to this, but I am not sure if it's really what I'm looking for.