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
{{ message }}
This repository has been archived by the owner on Mar 25, 2023. It is now read-only.
Currently we are using actix and are planning to move to hyper, but our application code must directly depend on either.
Currently all our HTTP request handlers take actix as input and output, which ties them too strongly with actix and switching away from actix is proving hard. We do not know what our eventual needs are going to be, so we can not pick a framework, so as much as possible we want to be as framework neutral as possible, so we can easily change framework when we need.
We will create fpm::http module with fpm::http::Request and fpm::http::Response types, which will be used by all our actual application code. And only fpm::http should know about which framework we are using.
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
-
Currently we are using
actix
and are planning to move tohyper
, but our application code must directly depend on either.Currently all our HTTP request handlers take actix as input and output, which ties them too strongly with
actix
and switching away from actix is proving hard. We do not know what our eventual needs are going to be, so we can not pick a framework, so as much as possible we want to be as framework neutral as possible, so we can easily change framework when we need.We will create
fpm::http
module withfpm::http::Request
andfpm::http::Response
types, which will be used by all our actual application code. And onlyfpm::http
should know about which framework we are using.Beta Was this translation helpful? Give feedback.
All reactions