Skip to content

#73 - Document that the state of a client persists between process executions in a worker - #74

Merged
njoubert-cleverage merged 1 commit into
mainfrom
73
Oct 21, 2026
Merged

njoubert-cleverage merged 1 commit into
mainfrom
73

Conversation

@njoubert-cleverage

Copy link
Copy Markdown
Member

Description

Fixes #73.

  • Client reference (Registration): a client service is shared, it keeps its state between two process executions in a long-running worker (Messenger, ui-process-bundle). A base URI changed with setUri() (never called by the bundle) is used by every following request and is not reset; the values specific to a request go in the request options of the task.
  • The setUri() row of the ClientInterface table links to this note.
  • CHANGELOG.

No ResetInterface: a reset() restoring the constructor URI would also undo a setUri() made in the calls of the service definition.

Documentation only. Checked in the container anyway (highest dependencies): 49 tests (1 skipped, as on main), 100 % of the lines, PHPStan, PHP-CS-Fixer and Rector OK.

Requirements

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

None: documentation only.

🤖 Generated with Claude Code

…ecutions in a worker

A client is a shared service: a base URI changed with setUri() is kept
by every following request of every process in a long-running worker.
Documented in the client reference (no ResetInterface: a reset would
undo a setUri() made in the calls of the service definition).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage
njoubert-cleverage merged commit 828a080 into main Oct 21, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document that the state of a client persists between process executions in a worker

1 participant