Package: collective.cdn.multiplehostnames
Table of ContentsCDN Support for Plone: Multiple HostnamesOverviewRequirementsInstallationUsageAdvanced UsageSponsoringCreditsChangelogCDN Support for Plone: Multiple HostnamesOverviewThis package provides support for a multiple hostnames CDN config for
Plone sites.Acting in a similar way to AlternateHostname provider, MultipleHostnames allows
you to type in multiple values for hostname.When the absolute_url method from a resource registry is called, we select one
of the available hostnames and return it to the browser.Using MultipleHostnames allows you to serve content from a hostname while
resources will be called from up to n other addresses.RequirementsPlone 3.3.x (http://plone.org/products/plone)Plone 4.0.x (http://plone.org/products/plone)Plone 4.1.x (http://plone.org/products/plone)Plone 4.2.x (http://plone.org/products/plone)collective.cdn.core (http://pypi.python.org/pypi/collective.cdn.core)InstallationTo enable this product,on a buildout based installation:Edit your buildout.cfg and addcollective.cdn.multiplehostnamesto the list of eggs to install[buildout]
...
eggs =
    collective.cdn.multiplehostnamesIf another package depends on the collective.cdn.multiplehostnames egg or
includes its zcml directly you do not need to specify anything in the
buildout configuration: buildout will detect this automatically.After updating the configuration you need to run the ‘’bin/buildout’’,
which will take care of updating your system.Go to the ‘Site Setup’ page in the Plone interface and click on the
‘Add/Remove Products’ link.Choose the CDN Support for Plone (check its checkbox) and click the ‘Install’ button.Uninstall – This can be done from the same management screen, but only
if you installed it from the quick installer.Note: You may have to empty your browser cache and save your resource
registries in order to see the effects of the product installation.UsageCDN settingsAfter installing this package, go to the ‘Site Setup’ page in the
Plone interface and click on the ‘CDN Configuration’ link.In this page you can choose which registries will use the CDN settings
by clicking the respective checkboxes.Choose the MultipleHostnames provider, add few hostnames, port number
and additional path –if needed – then save the settings.How it worksUsing the hostname provided in the settings page, we simply replace our
Plone site root’s url with the provided information.For example, let’s add two hostnames to our configs:cache01.simplesconsultoria.com.brcache02.simplesconsultoria.com.brWith port number 80 and an empty path, the link to
portal_css/beyondskins_simples/simplesconsultoria_site-cachekey0549.css
file would change from:http://www.simplesconsultoria.com.br/portal_css/beyondskins_simples/simplesconsultoria_site-cachekey0549.cssto:http://cache01.simplesconsultoria.com.br/portal_css/beyondskins_simples/simplesconsultoria_site-cachekey0549.cssThis is due to the algorithm used to choose between the available hostnames. If
the file was portal_css/beyondskins_simples/base-cachekey3443.css, the provider
would choose the second hostname.If we inform a port number different from 80, it will be appended to the
hostname, so with a port number of 8080, the above example would
return:http://cache01.simplesconsultoria.com.br:8080/portal_css/beyondskins_simples/simplesconsultoria_site-cachekey0549.cssThe same will happen if we inform a path in our settings. Using ‘simples’ as
our path, the first example would return:http://cache01.simplesconsultoria.com.br/simples/portal_css/beyondskins_simples/simplesconsultoria_site-cachekey0549.cssAdvanced UsageUsing a different path offers you the possibility of creating a simple
caching/cdn server for multiple sites. As an example we will consider we
have two Plone sites, www.simplesconsultoria.com.br and www.simplesnet.com.br,
and  we setup cache01.simples.srv.br and cache02.simples.srv.br as
hostnames in both Plone sites.In order to differentiate one site from the other we will set different paths
in each of them:simples in www.simplesconsultoria.com.brsimplesnet in www.simplesnet.com.brSo each site will have the following settings:www.simplesconsultoria.com.brProvider: MultipleHostnamesHostname: cache01.simples.srv.br, cache02.simples.srv.brPort: 80Path: simpleswww.simplesnet.com.brProvider: MultipleHostnamesHostname: cache01.simples.srv.br, cache02.simples.srv.brPort: 80Path: simplesnetAnd a link to a file portal_css/beyondskins_simples/base-cachekey3443.css,
would return for www.simplesconsultoria.com.br:http://cache02.simples.srv.br/simples/portal_css/beyondskins_simples/base-cachekey3443.cssAnd for www.simplesnet.com.br:http://cache02.simples.srv.br/simplesnet/portal_css/beyondskins_simples/base-cachekey3443.cssSo, our frontend server must rewrite calls tosimples/to
www.simplesconsultoria.com.br server and calls tosimplesnet/to the
www.simplesnet.com.br server.SponsoringDevelopment of this product was sponsored bySimples Consultoria.CreditsSimples Consultoria (products at simplesconsultoria dot com dot br) -
ImplementationDorneles Treméa for the invaluable talks about how to implement this
provider.Changelog0.6 (2012-08-01)Refactor tests to use plone.app.testing [ericof]0.5 (2011-02-21)Implementation of multiple hostnames provider [ericof]Initial release [ericof]