<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>DavidHLPL · RHINE LAB</title><description>DavidHLPL 的个人 AI 知识库，使用 LLM 持续整理可追溯的技术与工程知识</description><link>https://davidhlp.github.io/</link><language>zh-cn</language><item><title>chronicle.yaml</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/chronicle/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/chronicle/</guid><description>chronicle.yaml · src/content/information/zh-cn/chronicle.yaml</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>贺恋棚</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/introduction/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/introduction/</guid><description>贺恋棚 · src/content/information/zh-cn/introduction.md</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>知识库目录</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/kb-index/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/kb-index/</guid><description>知识库目录 · src/content/information/zh-cn/kb-index.md</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>知识库操作日志</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/kb-log/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/kb-log/</guid><description>知识库操作日志 · src/content/information/zh-cn/kb-log.md</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>linkroll.mdx</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/linkroll/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/linkroll/</guid><description>linkroll.mdx · src/content/information/zh-cn/linkroll.mdx</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>隐私政策</title><link>https://davidhlp.github.io/blog/legacy/information/zh-cn/policy/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/information/zh-cn/policy/</guid><description>隐私政策 · src/content/information/zh-cn/policy.md</description><pubDate>Mon, 05 Oct 2026 05:34:00 GMT</pubDate><category>zh-cn</category><category>information</category></item><item><title>数据库笔试复盘：从 SQL 语义到批量数据处理</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/database-written-test-review/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/database-written-test-review/</guid><description>把一套数据库笔试题复盘为可验证的判断链：先分清 SQL 语义与方言，再处理 NULL、重复与空结果，最后把 Kettle 和超大表操作落到分片、恢复、对账与风险控制。</description><pubDate>Sat, 12 Sep 2026 16:00:00 GMT</pubDate><category>数据库</category><category>SQL</category><category>Oracle</category><category>MySQL</category><category>Spark SQL</category><category>Kettle</category><category>ETL</category><category>笔试复盘</category><category>zh-cn</category><category>note</category></item><item><title>异步提前过期为什么只缩短 TTL：用版本 CAS 让旧任务自动失效</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-early-expiration-cas/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-early-expiration-cas/</guid><description>分析 ResiCache 如何用缓存值版本、Redis Lua CAS 和正常 miss 路径，避免旧异步任务误修改新缓存值。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>ResiCache</category><category>Redis</category><category>EarlyExpiration</category><category>CAS</category><category>Concurrency</category><category>zh-cn</category><category>note</category></item><item><title>ResiCache 的缓存责任链：控制流、嵌套 fragment 与 observer 生命周期</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-handler-chain-and-observer/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-handler-chain-and-observer/</guid><description>从 ResiCache 当前主线分析 HandlerResult、handler snapshot、锁内 fragment 与 observer scope token 如何共同保持缓存责任链的控制流和生命周期边界。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>ResiCache</category><category>Java</category><category>ChainOfResponsibility</category><category>Observer</category><category>ThreadLocal</category><category>Concurrency</category><category>zh-cn</category><category>note</category></item><item><title>换 Redis 序列化器不是改一行配置：从对象信任到可回滚迁移</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-serialization-migration/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-serialization-migration/</guid><description>从 ResiCache 的安全反序列化和迁移引擎分析，为什么 wire format、类型信任和存量数据迁移必须一起设计。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>ResiCache</category><category>Redis</category><category>Serialization</category><category>Security</category><category>Migration</category><category>zh-cn</category><category>note</category></item><item><title>缓存击穿时，为什么要同时有 Future、分布式锁和 double-check？</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-single-flight/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-single-flight/</guid><description>从 ResiCache 的加载路径分析 single-flight、分布式锁、double-check 和失败结果建模分别解决什么问题，以及它们不能保证什么。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>ResiCache</category><category>Redis</category><category>SingleFlight</category><category>Concurrency</category><category>DistributedLock</category><category>zh-cn</category><category>note</category></item><item><title>ResiCache：把缓存防护写成可验证的并发与一致性边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache/</guid><description>以 ResiCache 当前 main 的源码与边界测试为证据，提炼责任链、single-flight、版本化提前过期、白名单序列化和 observer 生命周期五个工程亮点，并明确与生产性能结论的距离。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>ResiCache</category><category>SpringCache</category><category>Redis</category><category>Concurrency</category><category>SingleFlight</category><category>Serialization</category><category>CAS</category><category>EarlyExpiration</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode 异步执行契约：idempotency、fingerprint 与有界 receipt</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-async-execution-contract/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-async-execution-contract/</guid><description>解释 UltiCode 如何让同步预览与异步执行共享 contract，并用幂等键、SHA-256 fingerprint、状态机和内存上限约束长任务。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>Async</category><category>Idempotency</category><category>Fingerprint</category><category>StateMachine</category><category>Judge0</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode 验证与供应链门禁：从 static contract 到可验证发布</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-ci-supply-chain/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-ci-supply-chain/</guid><description>提炼 UltiCode 如何将 zero-infra static contract、分层验证、Trivy、SBOM、provenance 与 Cosign 组织成可追溯的交付门禁。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>CI</category><category>StaticCheck</category><category>IntegrationTest</category><category>Trivy</category><category>SBOM</category><category>Cosign</category><category>Provenance</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>把模块化单体当实验场：UltiCode Core 的 Allowlist、超时与 Close-once 生命周期</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-core-bounded-testbed/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-core-bounded-testbed/</guid><description>从 UltiCode Core 的 owner context 管理器出发，解释如何用 opt-in、allowlist、有界启动和 close-once 交接，把模块化单体限制为可回滚的拓扑实验场。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>ModularMonolith</category><category>Lifecycle</category><category>ClassLoader</category><category>Allowlist</category><category>FailClosed</category><category>Testing</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode Docker 沙箱：资源隔离与基础设施错误分类</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-docker-sandbox/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-docker-sandbox/</guid><description>从 UltiCode 的 D-form 执行路径提炼 Docker 资源/安全参数、seccomp fail-closed 和用户错误与基础设施错误分类。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>Docker</category><category>Seccomp</category><category>Sandbox</category><category>ResourceLimit</category><category>ErrorHandling</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>数据库租约不够：UltiCode 用 Fence Token 拦住过期单例任务</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-fenced-singleton-lease/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-fenced-singleton-lease/</guid><description>从 UltiCode 的 fenced_job_leases 和 reconciliation run 写入路径出发，说明为什么只有租约过期时间还不够，以及 fence token 如何让旧执行者在数据库门口失效。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>FencedLease</category><category>DistributedLock</category><category>Reconciliation</category><category>CAS</category><category>MySQL</category><category>Concurrency</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode generation 与 attemptId：用条件更新拦截过期判题结果</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-generation-attempt-fence/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-generation-attempt-fence/</guid><description>用 UltiCode 的 generation、attemptId、租约和条件更新解释如何防止重判、超时或旧 Worker 的结果覆盖新状态。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>Generation</category><category>AttemptId</category><category>Lease</category><category>CAS</category><category>Concurrency</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode Outbox 与 Redis Streams：把判题投递做成可恢复状态</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-outbox-redis-streams/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-outbox-redis-streams/</guid><description>解释 UltiCode 如何用数据库 outbox、Redis Streams 原子投递、重试/死信和 PEL 回收，把判题消息从一次调用变成可恢复状态。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>Outbox</category><category>RedisStreams</category><category>Retry</category><category>DeadLetter</category><category>Idempotency</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode 数据 Owner 与事实快照：跨服务提交如何保持边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-owner-and-facts/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-owner-and-facts/</guid><description>从 UltiCode 的 owner 划分和 SubmissionFactsSnapshot 出发，说明跨服务写入如何把事实来源、捕获时间和 schema 版本变成显式契约。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>DataOwner</category><category>Contract</category><category>Port</category><category>Projection</category><category>Snapshot</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>跨 Owner 审计别靠跨库写入：UltiCode 的 Local Outbox 与 Consumer Inbox</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-owner-local-audit-inbox/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode-owner-local-audit-inbox/</guid><description>从 Auth/App 本地审计 outbox、owner-specific Redis Stream 到 Admin consumer inbox，解释跨 owner 审计如何处理双写、重复投递、租约恢复与最终一致性。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>Audit</category><category>DataOwner</category><category>Outbox</category><category>Inbox</category><category>RedisStreams</category><category>EventualConsistency</category><category>Idempotency</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>UltiCode：把在线评测做成可验证的工程系统</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/ulticode/</guid><description>以 UltiCode 当前 main 的固定提交为证据，解释 owner 边界、outbox 与 Streams、generation/attempt 围栏、Docker 沙箱和交付门禁如何组合成可验证的在线评测系统，并明确生产验证与性能结论的缺口。</description><pubDate>Tue, 08 Sep 2026 16:00:00 GMT</pubDate><category>UltiCode</category><category>OnlineJudge</category><category>DDD</category><category>Port</category><category>Projection</category><category>Outbox</category><category>RedisStreams</category><category>Docker</category><category>Seccomp</category><category>CI</category><category>LLM</category><category>zh-cn</category><category>note</category></item><item><title>Hindsight 本地算力分工与 Docker 容器化部署</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-local-deployment/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-local-deployment/</guid><description>记录 Vectorize Hindsight 记忆中枢的本地算力分工（AMD GPU 推理 + CPU Embedding）、UID 1000 权限模型与 Docker Compose 容器化编排。</description><pubDate>Sat, 22 Aug 2026 16:00:00 GMT</pubDate><category>Hindsight</category><category>Docker</category><category>Ollama</category><category>ROCm</category><category>BGE-M3</category><category>Architecture</category><category>zh-cn</category><category>note</category></item><item><title>Hindsight 统一记忆接入：FastMCP 桥接与多项目动态路由</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-omp-codex-integration/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-omp-codex-integration/</guid><description>详解 Hindsight 为 OMP 与 Codex 统一接入记忆的 FastMCP stdio 桥接状态机、Git 根目录自适应 Bank 动态路由及双端配置规范。</description><pubDate>Sat, 22 Aug 2026 16:00:00 GMT</pubDate><category>Hindsight</category><category>OMP</category><category>Codex</category><category>FastMCP</category><category>MCP</category><category>DynamicRouting</category><category>zh-cn</category><category>note</category></item><item><title>Hindsight 记忆系统运行时排障矩阵与失效模式</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-troubleshooting/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-troubleshooting/</guid><description>归纳 Hindsight 本地部署与 Agent 集成中的 7 大典型失效模式（假包、权限、超时、路由、Session丢失、工作区漂移）与排查矩阵。</description><pubDate>Sat, 22 Aug 2026 16:00:00 GMT</pubDate><category>Hindsight</category><category>Troubleshooting</category><category>Docker</category><category>Permissions</category><category>FastMCP</category><category>Ollama</category><category>zh-cn</category><category>note</category></item><item><title>Docker 基础：镜像分层、容器操作与 Compose 网络</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/docker-fundamentals/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/docker-fundamentals/</guid><description>归纳 Docker 镜像分层、常用命令、数据卷、网络与 Compose 的适用条件与边界。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Docker</category><category>Container</category><category>Compose</category><category>Image</category><category>Volume</category><category>Network</category><category>zh-cn</category><category>note</category></item><item><title>前端与综合随笔：Vue、MyBatis、UniApp、缓存注解与环境排障（已溶解归档）</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/frontend-mybatis-essays/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/frontend-mybatis-essays/</guid><description>历史随笔收纳袋已溶解。零散前端、MyBatis 与环境排障内容保留在不可变 raw 快照中，主知识库不再维护此综合页。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Vue</category><category>MyBatis</category><category>UniApp</category><category>Cache</category><category>Essay</category><category>Deprecated</category><category>zh-cn</category><category>note</category></item><item><title>HBase 基础、架构与运维：数据模型、表设计、Shell 与 Java API</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/hbase-foundation-and-ops/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/hbase-foundation-and-ops/</guid><description>收敛 HBase 数据模型（逻辑/物理）、架构组件、表设计与运维操作，明确与 Redis/传统 RDBMS 的取舍。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>HBase</category><category>BigData</category><category>DataModel</category><category>Architecture</category><category>Shell</category><category>JavaAPI</category><category>zh-cn</category><category>note</category></item><item><title>Java 并发深度：JUC、CAS、原子类、锁与线程机制</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-concurrency-deepdive/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-concurrency-deepdive/</guid><description>以 CAS 为内核，串联原子类、锁、线程协作与引用类型，明确无锁与有锁的适用成本。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Java</category><category>JUC</category><category>CAS</category><category>Concurrency</category><category>Lock</category><category>Thread</category><category>zh-cn</category><category>note</category></item><item><title>MySQL 存储引擎与死锁检测</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/mysql-storage-and-deadlock/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/mysql-storage-and-deadlock/</guid><description>区分存储引擎能力与死锁检测路径，提供存储选型与排障的最小判断。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>MySQL</category><category>StorageEngine</category><category>InnoDB</category><category>Deadlock</category><category>zh-cn</category><category>note</category></item><item><title>Redis 业务模式：缓存、分布式锁、消息队列、Feed 流与秒杀</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-business-patterns/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-business-patterns/</guid><description>以缓存一致性、锁正确性、消息语义为锚，收敛 Redis 在业务场景中的模式与反模式。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Redis</category><category>Cache</category><category>DistributedLock</category><category>MessageQueue</category><category>Feed</category><category>Seckill</category><category>zh-cn</category><category>note</category></item><item><title>Redis 黑马实战与进阶：分布式缓存、多级缓存与最佳实践</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-heima-practice/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-heima-practice/</guid><description>把黑马 Redis 实战提炼为分布式缓存、多级缓存与最佳实践的最小可用清单，标注版本与实验缺口。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Redis</category><category>Heima</category><category>DistributedCache</category><category>MultiLevelCache</category><category>BestPractice</category><category>zh-cn</category><category>note</category></item><item><title>Redis 持久化与原理：RDB/AOF、数据结构与高级机制</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-persistence-principle/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-persistence-principle/</guid><description>区分 RDB/AOF 持久化、底层数据结构与过期淘汰，明确持久化选择的可用性与性能边界。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Redis</category><category>Persistence</category><category>RDB</category><category>AOF</category><category>DataStructure</category><category>Principle</category><category>zh-cn</category><category>note</category></item><item><title>Spark 与大数据生态：Hadoop、HBase、Spark 运行模式与集群</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/spark-bigdata-ecosystem/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/spark-bigdata-ecosystem/</guid><description>对比分布式计算引擎，收敛 Spark 概述、运行模式与 Hadoop/HBase 集群搭建的最小验证。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>Spark</category><category>Hadoop</category><category>BigData</category><category>HBase</category><category>Cluster</category><category>zh-cn</category><category>note</category></item><item><title>Spring Boot 与 Spring Cloud：自动装配、事务、注册发现、网关与可观测性</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/spring-cloud-and-boot/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/spring-cloud-and-boot/</guid><description>以服务注册发现为起点，归纳自动装配、事务、熔断限流与可观测性的配置与运行边界。</description><pubDate>Thu, 20 Aug 2026 16:00:00 GMT</pubDate><category>SpringBoot</category><category>SpringCloud</category><category>Microservices</category><category>Gateway</category><category>Transaction</category><category>Observability</category><category>zh-cn</category><category>note</category></item><item><title>Hindsight 完全本地化部署与 OMP / Codex 统一记忆集成实践（已拆分归档）</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-local-deployment-and-agent-integration/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/hindsight-local-deployment-and-agent-integration/</guid><description>历史巨石页面已按 LLM-Wiki 原子化原则拆分为部署、接入与排障 3 个独立正典知识页。本页作为归档导引保留。</description><pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate><category>Hindsight</category><category>Memory</category><category>OMP</category><category>Codex</category><category>Deprecated</category><category>zh-cn</category><category>note</category></item><item><title>OMP Headroom Bridge：外部路由控制器与原生 Codex/OMP 代理边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-headroom-provider-proxy/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-headroom-provider-proxy/</guid><description>记录 OMP Headroom Bridge 如何用外部控制器维护 loopback Headroom、OMP provider route、原生 Codex CLI/Desktop Responses provider 和 Claude Code/cc-switch 共存边界。</description><pubDate>Thu, 13 Aug 2026 14:18:29 GMT</pubDate><category>OMP</category><category>Headroom</category><category>Codex</category><category>OpenCode</category><category>ClaudeCode</category><category>Proxy</category><category>Routing</category><category>systemd</category><category>Security</category><category>zh-cn</category><category>note</category></item><item><title>Headroom 与 cc-switch / Claude Code 共存：单一整理与安全边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-cc-switch-coexistence/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-cc-switch-coexistence/</guid><description>综合固定项目提交与运行时证据：Headroom 8787 如何在 cc-switch 15721 前承接 Claude Code Messages，保持 OMP 路径隔离、单一整理责任和可回滚的 systemd 安全边界。</description><pubDate>Thu, 13 Aug 2026 07:31:11 GMT</pubDate><category>Headroom</category><category>cc-switch</category><category>ClaudeCode</category><category>OMP</category><category>Anthropic</category><category>OpenAI</category><category>Proxy</category><category>Routing</category><category>Security</category><category>Compression</category><category>zh-cn</category><category>note</category></item><item><title>数据库 Schema 漂移：用 history、schema 与 query 三视图定位</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/database-schema-drift/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/database-schema-drift/</guid><description>说明 Flyway validate 为什么不能替代实际 Schema 检查，并用 migration history、实际 schema 与应用 query 三个视图区分 checksum 漂移、外部 DDL、Unknown column 和失败迁移残留。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Flyway</category><category>MySQL</category><category>Schema Drift</category><category>Migration</category><category>Database</category><category>Troubleshooting</category><category>zh-cn</category><category>note</category></item><item><title>Dubbo + Nacos：先核对注册名、group/version，再做真实 smoke test</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/dubbo-nacos-runtime/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/dubbo-nacos-runtime/</guid><description>基于 Apache Dubbo 3.3.6 与 Nacos 官方资料，说明接口级/应用级注册名、metadata、group/version 匹配、启动检查和真实 Nacos smoke test 的最小边界。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Apache Dubbo</category><category>Nacos</category><category>Service Discovery</category><category>Registry</category><category>RPC</category><category>Smoke Test</category><category>zh-cn</category><category>note</category></item><item><title>JJWT 0.13.0：显式固定签名算法，按 key 类型验签</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/jjwt-013-security-api/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/jjwt-013-security-api/</guid><description>说明 JJWT 0.13.0 中 signWith(Key) 的推荐算法启发式、双参数显式算法 API、verifyWith 的 SecretKey/PublicKey 类型边界，以及 audience builder 的迁移方式。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>JJWT</category><category>JWT</category><category>JWS</category><category>Security</category><category>HS256</category><category>RS256</category><category>Authentication</category><category>zh-cn</category><category>note</category></item><item><title>KB 会话摄入管道契约：增量复用、redaction v19 与不可变 raw</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/kb-session-ingest-contract/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/kb-session-ingest-contract/</guid><description>固定提交 c0ae74e 中 KB 会话摄入管道的最小契约：身份/内容哈希驱动增量复用、失败记录不复用、redaction v19、内部控制面过滤、partial checkpoint 断点续跑与 raw manifest 不可变校验，并澄清占位符语义与脱敏边界。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Knowledge Base</category><category>Ingestion</category><category>Redaction</category><category>Hashing</category><category>Manifest</category><category>Raw Evidence</category><category>zh-cn</category><category>note</category></item><item><title>MCP 协议时代边界与 codebase-memory-mcp v0.10.2 图工作流</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/mcp-codebase-memory-workflow/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/mcp-codebase-memory-workflow/</guid><description>MCP 2026-07-28 modern 逐请求 _meta 与 legacy initialize 握手的边界及错误码，以及 codebase-memory-mcp v0.10.2 的图搜索工作流：图结果不等于完整性证明，负面结论必须回到 coverage 与源码。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>MCP</category><category>Specification</category><category>Knowledge Graph</category><category>Code Intelligence</category><category>Workflow</category><category>Codebase Memory</category><category>zh-cn</category><category>note</category></item><item><title>微服务数据所有权：先定领域 owner，再谈拆库与迁移</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/microservice-data-ownership/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/microservice-data-ownership/</guid><description>用服务私有数据、bounded context、saga、transactional outbox 和 expand-migrate-contract 建立数据所有权判定顺序，避免把共享物理数据库、共享 schema 和服务自治混为一谈。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Microservices</category><category>Bounded Context</category><category>Data Ownership</category><category>Database-per-Service</category><category>Saga</category><category>Transactional Outbox</category><category>Strangler Fig</category><category>zh-cn</category><category>note</category></item><item><title>多服务启动就绪：running、ready 与依赖/失败/重启传播</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/multi-service-readiness/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/multi-service-readiness/</guid><description>用一张决策表区分多服务编排中的进程启动、业务就绪、排序、依赖建立、失败与重启传播六个概念，给出 Compose healthcheck/depends_on 与 systemd After/Wants/Requires 的最小组合和验证路径。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Docker Compose</category><category>systemd</category><category>depends_on</category><category>healthcheck</category><category>Readiness</category><category>Orchestration</category><category>zh-cn</category><category>note</category></item><item><title>Redisson/Jackson 对 LocalDateTime 的默认序列化行为与写读不对称边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-jackson-java-time/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/redis-jackson-java-time/</guid><description>说明默认 JsonJacksonCodec 与 GenericJackson2JsonRedisSerializer 为什么对 LocalDateTime 写入即失败、Redisson 默认 codec 实为 Kryo5Codec，以及按三层配置排查写读不对称的决策路径。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Redis</category><category>Redisson</category><category>Jackson</category><category>JavaTime</category><category>LocalDateTime</category><category>Spring Data Redis</category><category>Serialization</category><category>zh-cn</category><category>note</category></item><item><title>ResiCache：observer 嵌套执行必须区分生命周期、fragment 与 scope token</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-observer-nested-execution/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/resicache-observer-nested-execution/</guid><description>从公开 ResiCache 固定提交提炼 observer 生命周期、锁内 fragment、per-call scope token 与 ThreadLocal 快照隔离的边界，避免嵌套执行重复 hook 或污染并发状态。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Java</category><category>Observer</category><category>ThreadLocal</category><category>Concurrency</category><category>Redis</category><category>Cache</category><category>Reentrant</category><category>zh-cn</category><category>note</category></item><item><title>Testcontainers 1.20.6：先排查 Docker API 版本，再判断 daemon 不可用</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/testcontainers-docker-api/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/testcontainers-docker-api/</guid><description>说明 Testcontainers 1.20.6 如何将未知 Docker API 版本回退到 1.32、为什么 DOCKER_API_VERSION 不应套用 Docker CLI 经验，以及如何从最早的 400 错误区分版本不兼容和 Docker 环境缺失。</description><pubDate>Wed, 12 Aug 2026 16:00:00 GMT</pubDate><category>Testcontainers</category><category>Docker</category><category>docker-java</category><category>API-Version</category><category>Moby</category><category>Diagnostics</category><category>zh-cn</category><category>note</category></item><item><title>Headroom 0.34 压缩与检索契约：字段、模式与真实端点验证</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-compress-retrieve-contract/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-compress-retrieve-contract/</guid><description>固定 Headroom 0.34.0 的 /v1/compress 与 /v1/retrieve 请求、响应和模式边界，并说明为何真实 loopback contract test 必须与 mock 使用同一 schema。</description><pubDate>Tue, 11 Aug 2026 16:00:00 GMT</pubDate><category>Headroom</category><category>API</category><category>Compression</category><category>CCR</category><category>Contract Testing</category><category>Agent</category><category>zh-cn</category><category>note</category></item><item><title>知识库摄入收件箱</title><link>https://davidhlp.github.io/blog/legacy/jotting/zh-cn/kb-ingest-todo/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/jotting/zh-cn/kb-ingest-todo/</guid><description>尚未经过证据审查的来源和问题，只能作为摄入候选，不能当作稳定知识。</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>Knowledge Base</category><category>Ingest</category><category>TODO</category><category>zh-cn</category><category>jotting</category></item><item><title>LLM-Wiki 模式：用 LLM 增量维护一个持久的个人知识库</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/llm-wiki-pattern/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/llm-wiki-pattern/</guid><description>本页是 DavidHLPL 个人 AI 知识库的自我说明书，解释 raw、wiki、schema 三层和 ingest、query、lint 三个操作。</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>LLM</category><category>Knowledge Base</category><category>Wiki</category><category>RAG</category><category>Agent</category><category>zh-cn</category><category>note</category></item><item><title>Headroom 路由持久化综合：Named Profile、model_cache 与恢复</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-headroom-persistence/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-headroom-persistence/</guid><description>综合 OMP 更新重写运行时模型缓存时的 Headroom 路由持久化模型：Named Profile 隔离意图与凭据，外部声明保存路由意图，model_cache 作为可重建派生状态，旧 reconciler 只在隔离迁移中恢复并验证。当前 wrapper 生命周期与版本依赖明确标为 provisional。</description><pubDate>Wed, 05 Aug 2026 16:00:00 GMT</pubDate><category>OMP</category><category>Agent</category><category>Headroom</category><category>DevOps</category><category>LLM</category><category>Operations</category><category>Routing</category><category>Proxy</category><category>Codex</category><category>OpenCode</category><category>zh-cn</category><category>note</category></item><item><title>Headroom 单端口路由综合：入口、动态上游与验证边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-single-port-evolution/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/headroom-single-port-evolution/</guid><description>综合 Headroom 单端口路由的演进模型：一个 loopback 入口如何承接显式 custom provider、动态上游和不同协议，并把 OMP 角色选择、model_cache、请求级路由与 wrapper 生命周期分开验证。历史路由均标为 provisional。</description><pubDate>Fri, 31 Jul 2026 16:00:00 GMT</pubDate><category>OMP</category><category>Agent</category><category>Headroom</category><category>DevOps</category><category>LLM</category><category>Operations</category><category>Routing</category><category>Proxy</category><category>Codex</category><category>Kimi</category><category>MiniMax</category><category>Zhipu</category><category>zh-cn</category><category>note</category></item><item><title>SSH 内网访问方案：连接方向、暴露面与故障恢复</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/intranet-penetration-ssh-guide/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/intranet-penetration-ssh-guide/</guid><description>以连接方向、暴露面、控制平面、数据平面和故障恢复比较 Cloudflare Tunnel、Tailscale 与 FRP，并提炼移动端限制、端口语义和 systemd/linger 的可验证边界。</description><pubDate>Fri, 31 Jul 2026 16:00:00 GMT</pubDate><category>Intranet Penetration</category><category>Cloudflare</category><category>Tailscale</category><category>FRP</category><category>SSH</category><category>Termius</category><category>systemd</category><category>DevOps</category><category>zh-cn</category><category>note</category></item><item><title>OMP 配置分层：模型角色、Agent 覆盖与降级链</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-config-and-rules-guide/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-config-and-rules-guide/</guid><description>用可复用的分层模型解释 OMP 配置：modelRoles 负责角色默认路由，agentModelOverrides 负责局部覆盖，fallbackChains 负责故障后的恢复；同时划清 Headroom、规则发现与模型选择的边界，并给出按层验证的顺序。</description><pubDate>Fri, 31 Jul 2026 16:00:00 GMT</pubDate><category>OMP</category><category>Agent</category><category>Headroom</category><category>DevOps</category><category>LLM</category><category>Operations</category><category>RTK</category><category>Rules</category><category>Configuration</category><category>Architecture</category><category>zh-cn</category><category>note</category></item><item><title>OMP Hook 扩展概念：决策点提示、硬阻断与状态桥接</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-hook-extension-guide/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/omp-hook-extension-guide/</guid><description>把 OMP Hook 抽象为位于工具决策点的事件扩展：soft hook 用 sendMessage 提醒但不阻断，hard result 才能拒绝调用；setStatus 通过事件桥接到 UI。页面给出 API 边界、mock 与真实会话验证，并明确软提示不是安全强制边界。</description><pubDate>Fri, 24 Jul 2026 16:00:00 GMT</pubDate><category>Agent</category><category>OMP</category><category>Codebase</category><category>Hooks</category><category>DevOps</category><category>TUI</category><category>Plugin</category><category>Extension</category><category>zh-cn</category><category>note</category></item><item><title>MySQL 性能排查：现象→指标→定位层→安全缓解</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/mysql-performance-troubleshooting/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/mysql-performance-troubleshooting/</guid><description>把 MySQL 慢、卡、连接堆积和复制告警映射为现象、指标、定位层与安全缓解，覆盖连接、锁、索引、事务、Buffer Pool 和 IO，但不替代现场 SOP。</description><pubDate>Tue, 30 Jun 2026 16:00:00 GMT</pubDate><category>MySQL</category><category>Database</category><category>Troubleshooting</category><category>Performance</category><category>InnoDB</category><category>Operations</category><category>zh-cn</category><category>note</category></item><item><title>John Johnson · 2026-06-19-18-00-00</title><link>https://davidhlp.github.io/blog/legacy/preface/zh-cn/2026-06-19-18-00-00/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/preface/zh-cn/2026-06-19-18-00-00/</guid><description>John Johnson · 2026-06-19-18-00-00 · src/content/preface/zh-cn/2026-06-19-18-00-00.md</description><pubDate>Fri, 19 Jun 2026 10:00:00 GMT</pubDate><category>zh-cn</category><category>preface</category></item><item><title>百万级终端插件生命周期管理：状态、心跳与受控发布</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/plugin-lifecycle-management/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/plugin-lifecycle-management/</guid><description>把终端插件管理建模为一个可收敛的控制面：用 desired/current/ack/failure 状态机连接合并心跳、幂等调度、灰度熔断与故障恢复，并标出来源中的规模与能力假设。</description><pubDate>Mon, 01 Jun 2026 16:00:00 GMT</pubDate><category>Distributed Systems</category><category>Architecture Design</category><category>Endpoint Management</category><category>Canary Release</category><category>High Availability</category><category>zh-cn</category><category>note</category></item><item><title>Enhanced UISA：异构节点信息同步的 owner、边界与恢复模型</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/uisa-architecture-design/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/uisa-architecture-design/</guid><description>综合 Enhanced UISA 与插件生命周期来源，按 owner/boundary、同步协议、可靠性与幂等、异构节点、失败恢复和权衡重组一套可验证的控制面模型；不把来源中的规模与阈值当作生产承诺。</description><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><category>Architecture</category><category>Distribution</category><category>Security</category><category>Infrastructure</category><category>Sync</category><category>HybridCloud</category><category>zh-cn</category><category>note</category></item><item><title>containerd TLS：证书信任链与临时跳过验证的决策</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/containerd-tls-troubleshooting/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/containerd-tls-troubleshooting/</guid><description>用一条可验证的链路判断私有镜像拉取失败属于证书信任、Kubernetes 凭证还是节点缓存，并比较生产 CA 信任与临时 skip_verify 的边界。</description><pubDate>Tue, 24 Feb 2026 16:00:00 GMT</pubDate><category>Kubernetes</category><category>containerd</category><category>TLS</category><category>Harbor</category><category>Operations</category><category>Troubleshooting</category><category>zh-cn</category><category>note</category></item><item><title>Java 后端面试复盘：项目真实性、工程机制与生产证据</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-internship-interview-blog-polished/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-internship-interview-blog-polished/</guid><description>把项目真实性、缓存与异步机制、线上性能排障串成一套能力模型：先说明自己负责的事实，再解释工程取舍，最后用生产证据证明系统如何被验证和恢复。</description><pubDate>Tue, 24 Feb 2026 16:00:00 GMT</pubDate><category>Java</category><category>Backend</category><category>Internship Interview</category><category>Redis</category><category>Docker</category><category>Kafka</category><category>WebSocket</category><category>JVM</category><category>Production Troubleshooting</category><category>zh-cn</category><category>note</category></item><item><title>Java 线上性能排障：从症状到证据的最小决策树</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-online-performance-debug/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-online-performance-debug/</guid><description>把 Java 线上性能事故压缩为症状、证据、线程/GC/代码定位、止损与恢复的最小决策树，避免用重启或命令清单替代根因分析。</description><pubDate>Tue, 24 Feb 2026 16:00:00 GMT</pubDate><category>Linux</category><category>Operations</category><category>SRE</category><category>Performance Troubleshooting</category><category>CPU</category><category>Java</category><category>Production Incident</category><category>Arthas</category><category>JVM</category><category>Hot-Swapping</category><category>zh-cn</category><category>note</category></item><item><title>Donald Knuth · 2026-01-01-00-00-00</title><link>https://davidhlp.github.io/blog/legacy/preface/zh-cn/2026-01-01-00-00-00/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/preface/zh-cn/2026-01-01-00-00-00/</guid><description>Donald Knuth · 2026-01-01-00-00-00 · src/content/preface/zh-cn/2026-01-01-00-00-00.md</description><pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate><category>zh-cn</category><category>preface</category></item><item><title>NullValue：缓存 null 的占位对象与序列化边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-null-value/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-null-value/</guid><description>说明缓存层为什么需要区分 key 不存在与业务 null，NullValue 如何作为占位对象防御缓存穿透，以及单例和序列化在边界上的限制。</description><pubDate>Tue, 07 Oct 2025 13:43:00 GMT</pubDate><category>Java</category><category>Spring Cache</category><category>Caching</category><category>Null Object</category><category>Design Patterns</category><category>zh-cn</category><category>note</category></item><item><title>AtomicBoolean：原子布尔状态与 CAS 边界</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-atomic-boolean/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-atomic-boolean/</guid><description>说明何时需要原子布尔状态，compareAndSet 如何把检查与切换合并，以及 CAS 在多变量一致性、高竞争和复杂协作中的边界。</description><pubDate>Tue, 07 Oct 2025 12:25:00 GMT</pubDate><category>Java</category><category>Concurrency</category><category>AtomicBoolean</category><category>CAS</category><category>JUC</category><category>zh-cn</category><category>note</category></item><item><title>AutoCloseable：资源所有权与关闭异常语义</title><link>https://davidhlp.github.io/blog/legacy/note/zh-cn/java-auto-closeable/</link><guid isPermaLink="true">https://davidhlp.github.io/blog/legacy/note/zh-cn/java-auto-closeable/</guid><description>从资源所有权出发解释 AutoCloseable 与 try-with-resources 的关闭顺序、主异常和 suppressed 异常语义，并划定 close 幂等与失败处理边界。</description><pubDate>Tue, 07 Oct 2025 12:25:00 GMT</pubDate><category>Java</category><category>JDK</category><category>Exception Handling</category><category>Resource Management</category><category>Try-With-Resources</category><category>zh-cn</category><category>note</category></item></channel></rss>