fiber_hook
Lets you hook into `Fiber.new` and `Fiber.resume` (by BMorearty)
request_store-fibers
Lets you use `RequestStore` with a fiber-based server. (by BMorearty)
Our great sponsors
fiber_hook | request_store-fibers | |
---|---|---|
1 | 1 | |
2 | 5 | |
- | - | |
1.8 | 0.0 | |
over 2 years ago | over 2 years ago | |
Ruby | Ruby | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fiber_hook
Posts with mentions or reviews of fiber_hook.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-22.
-
Using RequestStore with asynchronous I/O in Rails apps
request_store-fibers is actually a thin layer on top of another more generic gem I wrote, fiber_hook, which does all the magic. It lets you hook into fiber creation and do anything you want right after any fiber is created and before it executes.
request_store-fibers
Posts with mentions or reviews of request_store-fibers.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-22.
-
Using RequestStore with asynchronous I/O in Rails apps
To fix this I wrote a new request_store-fibers gem that detects whenever a new fiber is created by hooking into Fiber.new. Before the fiber is executed, I copy the current request_store data into a variable. Then as soon as the fiber is resumed the very first time, I copy that data into the fiber's request_store.
What are some alternatives?
When comparing fiber_hook and request_store-fibers you can also consider the following projects:
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
falcon - A high-performance web server for Ruby, supporting HTTP/1, HTTP/2 and TLS.