<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CDN on Infinite Script</title><link>https://www.infinitescript.com/tags/cdn/</link><description>Recent content in CDN on Infinite Script</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 01 Jun 2019 06:50:36 +0000</lastBuildDate><atom:link href="https://www.infinitescript.com/tags/cdn/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerate WordPress with CDN and Cache Servers</title><link>https://www.infinitescript.com/2019/06/accelerate-wordpress-with-cdn-and-cache-servers/</link><pubDate>Sat, 01 Jun 2019 06:50:36 +0000</pubDate><guid>https://www.infinitescript.com/2019/06/accelerate-wordpress-with-cdn-and-cache-servers/</guid><description>&lt;p&gt;&#10;&#10;&lt;a href="https://www.infinitescript.com/2019/06/InfiniteScript-Architecture.webp" data-fancybox data-caption="InfiniteScript-Architecture"&gt;&#10; &lt;img src="https://www.infinitescript.com/2019/06/InfiniteScript-Architecture.webp" alt="InfiniteScript-Architecture" loading="lazy"&gt;&#10;&lt;/a&gt;&#10;&#10;&#10;&lt;/p&gt;&#10;&lt;p&gt;It has been a long time since I last wrote a blog post. In the past few days, I updated the architecture of Infinite Script to accelerate the speed for Chinese users. In this article, I share the new architecture of our website with you, illustrated in the figure above.&lt;/p&gt;&#10;&lt;h2 id="optimizing-a-cdn-for-static-content-delivery"&gt;Optimizing a CDN for Static Content Delivery&lt;/h2&gt;&#10;&lt;p&gt;Static content does not change over a period of time. If it does change, the changes are predictable. Static content includes images, CSS sheets, JavaScripts, and PDF files. Because of this, CDNs can cache a copy of the content at their edge servers. They can then serve it whenever a client requests it. CDNs are best at optimizing the delivery of static content from edge servers to users. Therefore, we use the CDN from &lt;a href="https://alibabacloud.com"&gt;Alibaba Cloud&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Use CDN Service in Spring MVC</title><link>https://www.infinitescript.com/2015/04/use-cdn-service-in-spring-mvc/</link><pubDate>Thu, 02 Apr 2015 15:53:52 +0000</pubDate><guid>https://www.infinitescript.com/2015/04/use-cdn-service-in-spring-mvc/</guid><description>&lt;p&gt;When I deployed &lt;a href="https://www.infinitescript.com/project/testzilla/"&gt;TestZilla&lt;/a&gt; on &lt;a href="https://www.aliyun.com"&gt;Aliyun&lt;/a&gt; Elastic Compute Service, growing traffic made it worth offloading static files (images, CSS, and JavaScript) to a CDN. At the time there was little guidance on wiring a CDN into Spring MVC, so I &lt;a href="https://stackoverflow.com/questions/28734196/how-to-use-cdn-in-spring-mvc"&gt;asked on Stack Overflow&lt;/a&gt; and ended up with the setup below. The idea is simple: keep the CDN host in a single property and inject it wherever your JSP views reference static assets.&lt;/p&gt;</description></item><item><title>Create CDN View Helper in Zend Framework 2</title><link>https://www.infinitescript.com/2015/02/create-cdn-view-helper-in-zend-framework-2/</link><pubDate>Thu, 26 Feb 2015 11:26:08 +0000</pubDate><guid>https://www.infinitescript.com/2015/02/create-cdn-view-helper-in-zend-framework-2/</guid><description>&lt;p&gt;In this article, you will learn how to create a custom view helper in Zend Framework 2. A concrete example will be used; a helper which generates links for a subdomain, intended for storing static files. This is especially useful if you wish to use a Content Delivery Network (CDN). With very little modification, the helper can be made generic to support links to subdomains for all purposes.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Zend Framework 2 has reached end of life. In 2019 the project moved to the Linux Foundation and was renamed &lt;a href="https://getlaminas.org/"&gt;Laminas&lt;/a&gt;, so the &lt;code&gt;Zend\&lt;/code&gt; namespaces below are now &lt;code&gt;Laminas\&lt;/code&gt; (for example &lt;code&gt;Zend\View\Helper\AbstractHelper&lt;/code&gt; becomes &lt;code&gt;Laminas\View\Helper\AbstractHelper&lt;/code&gt;). The view-helper mechanics are otherwise unchanged, so this post is kept as a historical walkthrough. For a real project, run the namespaces through the &lt;a href="https://docs.laminas.dev/migration/"&gt;Laminas migration guide&lt;/a&gt; and follow the current &lt;a href="https://docs.laminas.dev/laminas-view/v3/helpers/advanced-usage/"&gt;custom view helper docs&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>