<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>内容分发 on PlumePHP</title><link>https://plumephp.com/tags/%E5%86%85%E5%AE%B9%E5%88%86%E5%8F%91/</link><description>Recent content in 内容分发 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 13 Aug 2024 09:56:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E5%86%85%E5%AE%B9%E5%88%86%E5%8F%91/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏内容分发与资源版本架构设计</title><link>https://plumephp.com/game-server-content-delivery-architecture/</link><pubDate>Tue, 13 Aug 2024 09:56:00 +0800</pubDate><guid>https://plumephp.com/game-server-content-delivery-architecture/</guid><description>&lt;p&gt;内容分发看起来偏客户端，但服务端架构同样重要。资源版本、热更新包、CDN、灰度策略、最低版本限制、配置兼容，都需要服务端控制。资源包发错，可能导致客户端崩溃、协议不兼容或活动资源缺失。&lt;/p&gt;</description></item></channel></rss>