Skip to content
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.

Migration plan to other HTTP servers #211

Open
ubnt-intrepid opened this issue Dec 27, 2018 · 2 comments
Open

Migration plan to other HTTP servers #211

ubnt-intrepid opened this issue Dec 27, 2018 · 2 comments

Comments

@ubnt-intrepid
Copy link
Collaborator

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
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant