Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request context #111

Open
olegrok opened this issue Feb 18, 2020 · 2 comments
Open

Request context #111

olegrok opened this issue Feb 18, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@olegrok
Copy link
Contributor

olegrok commented Feb 18, 2020

As each request is handled in separate fiber it could be useful to store some information in fiber.storage (tarantool/tarantool#3462)

@Totktonada Totktonada added the feature A new functionality label Jan 12, 2022
@Totktonada
Copy link
Member

  1. There is the stash. The README shows how to get a captured part of the URL and give a brief API description without explanatons. In fact, it is inspired by Mojo and works in the similar way: you can store a value here and load it back later during the request processing (from a template as well).
  2. You can just use fiber.storage.

I'll consider this as the request to improve the documentation.

@Totktonada Totktonada added 1sp documentation Improvements or additions to documentation and removed feature A new functionality labels Jan 12, 2022
@olegrok
Copy link
Contributor Author

olegrok commented Jan 12, 2022

Yes, my initial thesis is not correct. All requests in the connection is handled by single fiber - it's an implementation detail of HTTP server. It's possible to use just fiber.storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants