tsukuyomi icon indicating copy to clipboard operation
tsukuyomi copied to clipboard

Migration plan to other HTTP servers

Open ubnt-intrepid opened this issue 5 years ago • 2 comments

Currently, there are two crates, tsukuyomi-server and tsukuyomi-service, in order to make the implementation of HTTP server separate from the role of Web framework (the behavior as an asynchronous function from an HTTP request to an HTTP response). these crates will be replaced the (official) HTTP server provided the community in the future. I want to migrate the server part in this project to another crate ASAP, but as it is difficult at the present time, it is necessary to consider the migration plan to another HTTP server.

ubnt-intrepid avatar Dec 27 '18 10:12 ubnt-intrepid

Candidates:

  1. Keep the current status and wait for appearing the new HTTP server(s).
  2. Deprecate tsukuyomi-server and use hyper and its abstraction directly.

ubnt-intrepid avatar Dec 27 '18 10:12 ubnt-intrepid

Note: I created a new project based on tsukuyomi-server, with the aim of using it in other frameworks: https://github.com/ubnt-intrepid/izanami

ubnt-intrepid avatar Jan 10 '19 04:01 ubnt-intrepid