This is a channel for requesting and receiving data. Each channel has only one requesting end, but it can have multiple responding ends. It is useful for implementing work sharing. The two ends of the channel are asynchronous with respect to each other, so it is kinda nonblocking. However, if multiple responding ends try to respond to the same request, only one will succeed; the rest will return errors.
API for Cortex, a powerful observable analysis and active response engine.
A crate for calculating Net Promoter Score (NPS) from survey responses.
An actix-web responder for rust-embed that implements cache revalidation and compressed responses.
An attribute macro to transform a response struct to an actix responder
Embed static resources (GUI, assets, images, styles, html) within executable. Serve with hyper or any server of your choice.
In-process mock OCSP responder for integration tests, with configurable Good / Revoked / TryLater statuses.
Quickly create API:s using this simple and lightweight framework.
An asynchronous duplex communication channel between multiple clients and a single responder in different asynchronous blocks.
A set of htmx extractors, responders, and request guards for axum.
Libcrux Pre-Shared post-Quantum key establishement protocol
A minimal HTTP responder
Make API responses hella simple
Backport of Rails 3 respond_with functionality
first write for none standar database + active_admin app and then open as a gem
Sometimes it causes some trouble. Take that as read. This will let you know when you slip, and include respond_with.
We miss the respond_with_content_type matcher in shoulda-matchers.
Add i18n and some more magick to the responses with respond_with
This extension makes all sinatra routes automatically call to_json on whatever the routes block evaluates to
respond_with gon
`bounce` will save and return an active record object. This results in a nice refactor of update and create actions in your controllers when used with `respond_with`.
Use roar representers with respond_with in a way that you can easily use multiple representers for the same model and for the same controller but without being mandatory. Support ActiveRecord, Mongoid, and any Ruby object that responds to `to_model` and `model_name`.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.