<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>OnlyOffice on Tangc.pro&#39;s blog</title>
    <link>https://tangc.pro/blog/tags/onlyoffice/</link>
    <description>Recent content in OnlyOffice on Tangc.pro&#39;s blog</description>
    <image>
      <title>Tangc.pro&#39;s blog</title>
      <url>https://tangc.pro/blog/cover.png</url>
      <link>https://tangc.pro/blog/cover.png</link>
    </image>
    <generator>Hugo -- 0.157.0</generator>
    <language>zh-cn</language>
    <managingEditor>onetick@live.cn (Hongyu)</managingEditor>
    <webMaster>onetick@live.cn (Hongyu)</webMaster>
    <lastBuildDate>Sat, 15 Nov 2025 09:00:00 +0800</lastBuildDate>
    <atom:link href="https://tangc.pro/blog/tags/onlyoffice/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>踩坑实录：ONLYOFFICE forcesave 的同步化处理</title>
      <link>https://tangc.pro/blog/posts/onlyoffice-forcesave-sync/</link>
      <pubDate>Sat, 15 Nov 2025 09:00:00 +0800</pubDate><author>onetick@live.cn (Hongyu)</author>
      <guid>https://tangc.pro/blog/posts/onlyoffice-forcesave-sync/</guid>
      <description>一次因 forcesave 异步特性导致数据不一致的惨痛教训，以及使用 Redisson CountDownLatch 实现同步等待的解决方案</description>
    </item>
    <item>
      <title>当 if-else 长成一棵树：用策略模式重构 OnlyOffice 回调处理</title>
      <link>https://tangc.pro/blog/posts/strategy-pattern-refactoring/</link>
      <pubDate>Thu, 13 Nov 2025 15:30:00 +0800</pubDate><author>onetick@live.cn (Hongyu)</author>
      <guid>https://tangc.pro/blog/posts/strategy-pattern-refactoring/</guid>
      <description>面对 OnlyOffice 多种回调类型的处理，从 Service 层堆积的 if-else 到策略模式的优雅重构，一次设计模式的实战应用。</description>
    </item>
  </channel>
</rss>
