You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey !
I'm currently on a migration to hyper 1.0 for my project (Totodore/socketioxide#126). It is a socket.io server implementation as a Tower layer / Service. The main purpose of this migration is to support salvo but I need to keep backward compatibility so it can integrates with Axum or Warp.
Because hyper now has its custom Service type I can just implement this new one and also keep the tower service implementation.
However my main issue is with Body types between http-body 1.0 and http-body 0.4 I cannot keep backward compatibility with that. I don't know if I could make a common trait or something like that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey !
I'm currently on a migration to hyper 1.0 for my project (Totodore/socketioxide#126). It is a socket.io server implementation as a
Tower layer/Service. The main purpose of this migration is to support salvo but I need to keep backward compatibility so it can integrates withAxumorWarp.Because hyper now has its custom
Servicetype I can just implement this new one and also keep the tower service implementation.However my main issue is with
Bodytypes between http-body 1.0 and http-body 0.4 I cannot keep backward compatibility with that. I don't know if I could make a common trait or something like that.Does anyone has experienced similar issues ?
Beta Was this translation helpful? Give feedback.
All reactions