@rsc-kit/mcp 0.27.1 → 0.28.1

package/guides/deployment.md

@@ -162,7 +162,7 @@ stacks on top of it.
 
 ## Streams and idle timeouts
 
-An `events()` route and the [`refreshOn`](/guides/sections#refreshing-on-a-change-from-outside)
+An `events()` route and the [`refreshOn`](/guides/live-data)
 stream hold a connection open and are quiet most of the time. Anything in
 front that closes a quiet connection - the server's idle timeout, a proxy's
 read timeout - would cut them, so each sends a keepalive line every **eight
@@ -189,7 +189,7 @@ one as another, so one leaking does not hand out the rest.
 | Variable | What it protects | Who needs it | Read by |
 | --- | --- | --- | --- |
 | `RSC_HOST_CALL_SECRET` | calls between the renderer and a Go or Laravel backend | an app with a backend - required | the renderer **and** the backend |
-| `RSC_SIGNING_SECRET` | the names a page hands a tab for [`refreshOn`](/guides/sections#refreshing-on-a-change-from-outside) | an app that uses `refreshOn` - required in production | the renderer |
+| `RSC_SIGNING_SECRET` | the names a page hands a tab for [`refreshOn`](/guides/live-data) | an app that uses `refreshOn` - required in production | the renderer |
 | `RSC_ACTION_ENCRYPTION_KEY` | values a server action sends through the browser, [across a deploy](#server-actions-across-a-deploy) | optional | the renderer, from the build |
 
 `bun create rsc-kit` and `rsc-kit init` generate the first two into `.env` for

package/guides/go.md

@@ -286,7 +286,7 @@ reg.Names(&rsckit.SQLTags{DB: db, Placeholder: rsckit.Dollar})   // Postgres; ni
 
 Anything with a `Bump` and a `Versions` fits. Set `RSC_SIGNING_SECRET` for the renderer, the same on every instance:
 it signs the names a page hands the tab, and is not the host-call secret.
-Generating and rotating both: [Secrets](/hosts/deployment#secrets). [Sections](/guides/sections#refreshing-on-a-change-from-outside)
+Generating and rotating both: [Secrets](/hosts/deployment#secrets). [Sections](/guides/live-data)
 has the whole picture.
 
 ## Production

package/guides/index.json

@@ -124,6 +124,11 @@
     "title": "Laravel",
     "description": "React Server Components in front, a Laravel application behind them."
   },
+  {
+    "slug": "live-data",
+    "title": "Live data",
+    "description": "Keep what a page shows current as the data changes - refreshOn, events, polling."
+  },
   {
     "slug": "mcp",
     "title": "Working with an AI agent",

package/guides/laravel.md

@@ -358,28 +358,40 @@ later. Set `RSC_SIGNING_SECRET` for the renderer, the same on every instance:
 it signs the names a page hands the tab, and is not the host-call secret.
 Generating and rotating both: [Secrets](/hosts/deployment#secrets).
 
-**Watching without PHP.** By default the renderer asks PHP which versions
-moved, every couple of seconds while any tab is watching. Keep the versions in
-the `rsc_versions` table instead and the renderer reads them itself:
+**What watching costs PHP.** The renderer asks Laravel which versions moved
+once for every tab it serves, not once per tab: one request about every two
+seconds per renderer process while any tab is watching, each a cache read.
+Three renderers are one or two small requests a second for the whole fleet.
+That is the default and the recommendation - Laravel stays the only thing
+that talks to its database.
+
+**Keeping versions in a table** (`RSC_VERSIONS=database`) is for when you
+want them in the database rather than the cache: pruned on a schedule with
+`rsc:prune-versions`, or written by something outside Laravel - a Go service,
+a worker in another language - through the [shared table](/guides/live-data#the-table).
+Laravel still answers the renderer from it; nothing else changes.
 
 ```sh
 php artisan vendor:publish --tag=rsc-migrations && php artisan migrate
 RSC_VERSIONS=database
 ```
 
-```ts title="src/instrumentation.ts"
-import { installVersionSource, postgresVersions } from '@rsc-kit/core/changed'
-import postgres from 'postgres'
+**Instant, with broadcasting.** If the app has Laravel's broadcasting set up
+(`php artisan install:broadcasting`) with a server that speaks the Pusher
+protocol - Reverb, Pusher, Soketi - each `Rsc::changed()` can announce itself,
+and the renderer asks the moment it hears:
 
-export function register() {
-  installVersionSource(postgresVersions(postgres(process.env.DATABASE_URL!)))
-}
+```sh
+RSC_BROADCAST=true                      # Laravel: announce every change
+RSC_BROADCAST_URL=wss://ws.example.com  # the renderer: where to listen
+RSC_BROADCAST_KEY=your-app-key          # the renderer: the server's app key
 ```
 
-Watching then costs PHP no requests, and on Postgres `Rsc::changed()` sends a
-NOTIFY, so tabs hear it at once. On MySQL use `sqlVersions` with your driver;
-the renderer reads the table once a second. [Sections](/guides/sections#refreshing-on-a-change-from-outside) has the
-whole picture.
+A change then reaches the tabs at once, and between changes the renderer asks
+only every thirty seconds, as a safety net. The announcement carries nothing -
+the channel is public, and names may be one visitor's - so Laravel still
+answers which names moved, and the renderer never touches the database. It is
+sent after the transaction commits.
 
 ## Route middleware