By serving images/files to the client, I assume you mean static files css, js etc.
Most of the time, a simple solution is the best solution. Just host them on a different server under a different subdomin, i.e. http://content.mydomain.com/img/xyz.jpg. You could host them at a data centre on dedicated server giving your perforamace (close to the backbone), you could load balance the url and by have 2+ servers at 2+ different data centers, giving you resilliance and scalability.
You maintence task is then having todo find a replace when promoting your site to live to replace dev/uat content paths with the live content path (tho you'd only need todo this in css files as you could store the paths for content used within aspx files for as config data).
发布评论
评论（1）
通过向客户端提供图像/文件，我假设您指的是静态文件 css、js 等。
大多数时候，简单的解决方案是最好的解决方案。只需将它们托管在不同子域下的不同服务器上，即 http://content.mydomain.com /img/xyz.jpg。您可以将它们托管在专用服务器上的数据中心，提供您的性能（靠近主干网），您可以对 URL 进行负载平衡，并在 2 个以上不同的数据中心拥有 2 个以上服务器，从而为您提供弹性和可扩展性。
然后，您的维护任务是在将站点升级为实时时必须找到替换，以将 dev/uat 内容路径替换为实时内容路径（您只需要在 css 文件中执行此操作，因为您可以存储在其中使用的内容的路径） aspx 文件作为配置数据）。
By serving images/files to the client, I assume you mean static files css, js etc.
Most of the time, a simple solution is the best solution. Just host them on a different server under a different subdomin, i.e. http://content.mydomain.com/img/xyz.jpg. You could host them at a data centre on dedicated server giving your perforamace (close to the backbone), you could load balance the url and by have 2+ servers at 2+ different data centers, giving you resilliance and scalability.
You maintence task is then having todo find a replace when promoting your site to live to replace dev/uat content paths with the live content path (tho you'd only need todo this in css files as you could store the paths for content used within aspx files for as config data).