recapi 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d12730fb7a1d92afff5bc3b2b2383830df795b24fada7104fd8e66c3ac84dc9a
-  data.tar.gz: 5accff282fae359cb6fe664dbebf5957b351df0d155199ce04fa145049ffe3d4
+  metadata.gz: dfb3a3778d3f1733138f9f09c388edfd2e7cb946f6a2f38647b1070aa885d865
+  data.tar.gz: cc7d5eed12f41976d3e898a43bfee08364eaf2224b23f36b062b101577f7cb06
 SHA512:
-  metadata.gz: eb5e428dd2fe97d7bdc35da5838b84bbcf68b1ece0ee137b8bbdd0dd4b75f24d0b3f30f01d392416a2e4034efa94ac8adc1aaceb570366b46fbf8b9012ea5646
-  data.tar.gz: 71cc4af3ea8dd8b424c54e4cf69b94ec50c288fc0dbb7370797064d67cd9d40d06b56c46f94c8d92dd87a237653ef8a808ece2a0c523950ee994d14af2f2ba8b
+  metadata.gz: b48b41679b86910bb139237e630e5495bebfc4d1aa4fd9f924c2202344e5fbb903fb4c3966e5c608ffa406a90a2cb97c6a3fb75a989091509a41709f257e614f
+  data.tar.gz: b711bee7d27e579947e075e02a3e4487a97a2b7fe433e4d067d035d5b747157cd2cec7efa1adf34f6bd62bc1dd4d0e63ceb8f5612eb90bb929b1282a981f4051

data/README.md

@@ -16,24 +16,28 @@ passes the shared vectors in [`spec/`](../../spec).
 
 ## Install
 
-Until the library is published as a gem, recapi serves it as one file (the
-dashboard's quick start shows the line with your address). In a Rails app,
-save it as `lib/recapi.rb`:
+The library is the gem `recapi` on RubyGems (production releases publish it:
+[docs/deployment.md](../../docs/deployment.md#publishing-the-ruby-library)):
+add `gem "recapi"` to your Gemfile, or
 
 ```sh
-curl -fLo lib/recapi.rb https://api.<your-domain>/sdk/ruby/recapi-0.1.3.rb
+bundle add recapi
 ```
 
-Once it is published on RubyGems (production releases publish it:
-[docs/deployment.md](../../docs/deployment.md#publishing-the-ruby-library)),
-`gem "recapi"` in your Gemfile, or `gem install recapi`, installs the same
-file as a gem, and `require "recapi"` loads it.
+and `require "recapi"` loads it (Rails does it for you). Without access to
+RubyGems, recapi serves the same file (the dashboard's quick start shows the
+line with your address): save it as `lib/recapi.rb` and
+`require Rails.root.join("lib/recapi").to_s` instead.
+
+```sh
+curl -fLo lib/recapi.rb https://api.<your-domain>/sdk/ruby/recapi-0.1.4.rb
+```
 
 ## Quick start
 
 ```ruby
 # config/initializers/recapi.rb: one client per process, shared by its threads.
-require Rails.root.join("lib/recapi").to_s
+require "recapi"
 
 # A secret key (rk_sec_…): it stays on your server.
 RECAPI = Recapi::Client.new(ENV.fetch("RECAPI_KEY"), "https://api.example.com",
@@ -78,7 +82,13 @@ max_batch:, logger:)` sets the options. The default `Recapi::MemoryStore`
 keeps the 10,000 most recent users in the process; pass `Rails.cache` (it
 has `read`/`write`/`delete`) or a Redis client (`get`/`set`/`del`) when
 several processes serve the same users. It stores the same JSON as the
-Python library, so both can share one store. Puma's threads share one
+Python library, so both can share one store. Written to `Rails.cache` or a
+redis-rb client, a user's state lasts 30 days from its last write, with no
+setting to choose: well past the 24 hours a click earns credit, and recapi gives
+a known `user_id` its history back afterwards. Any other store gets a plain
+`set`/`write`, including a client wrapped in `ConnectionPool::Wrapper`: make it
+expire entries itself after about 30 days, or Redis keeps them for ever. Puma's
+threads share one
 client; a forked worker (Puma cluster, Unicorn, Passenger) starts its own
 queue and sender at its first call. Proxies come from `HTTPS_PROXY`,
 `HTTP_PROXY` and `NO_PROXY`, as `Net::HTTP` reads them. Failures are logged

data/lib/recapi.rb

@@ -25,7 +25,7 @@ rescue LoadError
 end
 
 module Recapi
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 
   # Decayed user history, exactly as docs/history-spec.md (times in unix ms).
   # A port of sdk/python's history.py, snapshot merging included.
@@ -389,6 +389,15 @@ module Recapi
     # Shown items remembered per user.
     MAX_SHOWN_ITEMS = 100
     PUBLIC_KEY_PREFIX = "rk_pub_"
+    # How long a recognised shared store keeps a user's state after its last
+    # write. Far beyond the 24 hours of click credit, and by then a score has
+    # halved four times (under 5% is left). A known user_id gets its history
+    # back from recapi, which keeps 90 days, so only a visitor gone for a month
+    # starts afresh. It bounds a Redis at about one month's visitors instead of
+    # growing for ever.
+    STATE_LIFETIME_SECONDS = 30 * 24 * 60 * 60
+    # Where redis-rb defines set: 4.x and 5 on, older versions, Redis::Distributed.
+    REDIS_RB_SET = %w[Redis::Commands::Strings Redis Redis::Distributed].freeze
     # Open connections kept between calls: one per call in flight at the busiest moment.
     MAX_IDLE_CONNECTIONS = 16
     CODE_BY_STATUS = {
@@ -435,6 +444,7 @@ module Recapi
       end
 
       @store = store || MemoryStore.new
+      @store_lifetime = store_lifetime
       @timeout = timeout.to_f
       @interval = flush_interval.to_f
       @max_batch = max_batch.to_i.clamp(1, MAX_EVENTS_PER_REQUEST)
@@ -1010,11 +1020,26 @@ module Recapi
       @logger.error("recapi: store write failed: #{e.class}: #{e.message}")
     end
 
+    # What makes this store's write expire the entry. By class name, since the
+    # library requires neither gem. Any doubt (a subclass's own set, a wrapper
+    # such as ConnectionPool::Wrapper) means no option, as for a store of the
+    # customer's.
+    def store_lifetime
+      klass = @store.class
+      if klass.public_method_defined?(:set)
+        REDIS_RB_SET.include?(klass.instance_method(:set).owner.name) ? { ex: STATE_LIFETIME_SECONDS } : {}
+      elsif klass.ancestors.any? { |ancestor| ancestor.name == "ActiveSupport::Cache::Store" }
+        { expires_in: STATE_LIFETIME_SECONDS }
+      else
+        {}
+      end
+    end
+
     # Redis clients have get/set/del, Rails.cache read/write/delete.
     def store_call(action, key, value = nil)
       case action
       when :get then @store.respond_to?(:get) ? @store.get(key) : @store.read(key)
-      when :set then @store.respond_to?(:set) ? @store.set(key, value) : @store.write(key, value)
+      when :set then @store.respond_to?(:set) ? @store.set(key, value, **@store_lifetime) : @store.write(key, value, **@store_lifetime)
       else @store.respond_to?(:delete) ? @store.delete(key) : @store.del(key)
       end
     end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: recapi
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - recapi
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-11-02 00:00:00.000000000 Z
+date: 2026-11-04 00:00:00.000000000 Z
 dependencies: []
 description: 'Ruby client for the recapi recommendation API: per-user history, event
   batching, retries, popular fallback. Standard library only.'