Async mutex lock for managing access to a shared resource
Asynchronous resources shared across async callchain via async_hooks
shared resource across repos.
a shared resource for auth utilities
Shared resource for Montu backend services
Async mutex lock for managing access to a shared resource
Retrieve a lock for a specific node instance to provide mutually exclusive access to a shared resource
Exclusive, stackable locking to control concurrent access to shared resource(s)
A mutex for guarding async workflows
This library is intended to be used as a shared resource for types, models, and interfaces across the DailyOM Suite applications. It helps maintain consistency and reusability of types throughout the codebase. Make sure to keep the types well-documented a
Shared resource for Montu backend services
Compile `using` and `await using` declarations to ES2015
Shared resource for the monorepo for experimentation
Is this value a JS SharedArrayBuffer?
A simple reuse pool of one. Makes automatic cleanup of a single shared resource (think db connection) easy.
a single-function package that constructs a function gaining exclusive access to some shared resource
OpenTelemetry SDK resource detector for Azure
A component decorator that makes it easy to create and re-use react-three-fiber resources like materials and geometries.
OpenTelemetry SDK resource detector for GCP
OpenTelemetry resource detector for Alibaba Cloud
internal utils shared across @vue packages
Opentelemetry resource detector to get container resource attributes
OpenTelemetry SDK resources
OpenTelemetry SDK resource detector for AWS
A library for safely transitioning through the three phases of shared resource access: setup, read, and cleanup.
Distributed locks for Rust with multiple backend support (PostgreSQL, Redis, MySQL, MongoDB, file system)
Core traits and types for distributed locks
File system backend for distributed locks using OS-level file locking
MongoDB backend for distributed locks using atomic updates and TTL indexes
MySQL backend for distributed locks using GET_LOCK/RELEASE_LOCK functions
PostgreSQL backend for distributed locks using advisory locks
Redis backend for distributed locks with RedLock algorithm support
Wrapper for a resource that can be shared across processes.
Create thread pools with a shared resource.
Shared resources for ZKsync node framework
Middleware that will make Rack-based apps CORS compatible. Fork the project here: https://github.com/cyu/rack-cors
Cross Origin Resource Sharing helper for Sinatra
Dashboards, articles, reports... can be models that users share. We help you to do it easily.
Shared PatientBank CSS and Javascript resources.
Shared resources for VA Caseflow applications
Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!
A Ruby C extention that is used to control access to shared resources across process boundaries with SysV semaphores.
Core shared models, tasks, and other resources for bitsmith.
Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!
This is a Strelka application plugin for describing rules for [Cross-Origin Resource Sharing (CORS)](http://www.w3.org/TR/cors/). NOTE: It's still a work in progress. By default, the plugin has paranoid defaults, and doesn't do anything. You'll need to grant access to the resources you want to share. To grant access, you declare one or more `access_control` blocks which can modify responses to matching access-control requests. All the blocks which match the incoming request's URI are called with the request and response objects in the order in which they're declared: # Allow access to all resources from any origin by default access_control do |req, res| res.allow_origin '*' res.allow_methods 'GET', 'POST' res.allow_credentials res.allow_headers :content_type end These are applied in the order you declare them, with each matching block passed the request if it matches. This happens before the application gets the request, so it can do any further modification it needs to, and so it can block requests from disallowed origins/methods/etc. There are a number of helper methods added to the request and response objects for applying and declaring access-control rules when this plugin is loaded:
Gem that focus on making a public site's resources very quickly while being very configurable!, supports facebook sharing, instagram and google analytics integration
Allows a simple declarative idiom for accessing resources in controllers and views via a well-defined interface that increases testability and reduces shared state.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.