Skip to content

Add cache-control force release support#119

Closed
mitonize wants to merge 6 commits intodevelop-2.0from
feature/replace_caching
Closed

Add cache-control force release support#119
mitonize wants to merge 6 commits intodevelop-2.0from
feature/replace_caching

Conversation

@mitonize
Copy link
Collaborator

@mitonize mitonize commented Mar 1, 2026

Summary\n- add force release operation to cache control registry\n- expose operation via CacheControlMXBean API\n- document management operation updates\n\n## Notes\n- this PR contains currently staged management/cache-control changes only

mitonize added 6 commits March 1, 2026 17:57
NamespaceImpl のインスタンスキャッシュ(ReferenceCache)を撤去し、実装を copy ベースに整理。\n\n背景/根拠:\n- NamespaceImpl.getInstance(...) の実呼び出しは存在せず、参照はコメントアウトのみ。\n- SpecificationUtil.getFixedNamespace(...) は original をそのまま返しており、固定化キャッシュの導線は実質無効。\n- Namespace の主要実体は SpecificationNodeImpl 側で保持され、NamespaceImpl 単独はパース時の一時スコープ用途が中心。\n- そのため singleton/intern キャッシュ層は実効性が低く、理解コストのみ増やしていた。\n\n変更内容:\n- NamespaceImpl から ReferenceCache 依存と getInstance API を削除。\n- copyOf は親 Namespace を再帰 copy する方式に変更。\n- deserialize 内の旧キャッシュ登録処理を削除。\n- 旧 getInstance 参照のコメントを SpecificationUtil / TemplateBuilderImpl から削除。\n\n互換性:\n- Namespace の公開契約(振る舞い)は維持。\n- test-compile 通過を確認済み。
- remove local source-script cache from AbstractServiceCycle\n- add SourceCompiledScript cache in ScriptEnvironmentImpl\n- register SourceCompiledScript cache to CacheControllerRegistry\n- normalize null encoding for stable cache key
@mitonize mitonize changed the base branch from master to develop-2.0 March 1, 2026 14:07
@mitonize mitonize closed this Mar 1, 2026
@mitonize mitonize deleted the feature/replace_caching branch March 1, 2026 14:12
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.

1 participant