#cdnjs

The CDNJS – Hosted Libraries custom tag template is a tag template for Google Tag Manager’s community template gallery. Description You can use this template to load third-party libraries from the CDNJS content distribution network. There is a preset list of the most popular libraries, and you can also just provide a path to the library manually. If you use the drop-down list to select the…

cdnjs 轉移到 Cloudflare 負責維護

不確定是 cdnjs 還是 CDNJS，因為官方網站是小寫，但 GitHub 上是大寫…

Anyway，cdnjs 本來由社群維護更新 (實際上是透過 bot 更新，但 bot 本身也需要維護)，因為人力時間的因素，轉移給 Cloudflare 負責了：「An Update on CDNJS」。

這次也更新了 cdnjs 的 daily request 數量，可以看到現在大約是每天六十億次：

本來 Cloudflare 是站在贊助頻寬的角色提供服務：

Within Cloudflare’s infrastructure there is a set of machines which are responsible for pulling the latest version of the repo periodically. Those machines then become…

Comme vous avez pu le remarquez certaines bibliothèques peuvent utiliser beaucoup de bande passante pour le seul fait de charger. C'est pourquoi UN CDN peut être pratique pour ces cas-ci.

Un CDN c'est quoi?

Un CDN (Content Delivery Network),   sont des serveurs qui ne servent qu’ à délivrer du contenu (image,video, librairie …). Le gros intérêt, c’est qu’un CDN va optimiser la livraison des données en fonction de la position géographique.

To my surprise, my wife's web site on Google App Engine had a surprisingly bad uptime this month as measured by Pingdom (about 96% uptime).  This helped to push me to actually get a site out on Heroku using the Play 2.0 framework.  The result is Folkerts Fotografie.

To improve performance and security, the site is using CloudFlare and their content delivery network, cdnjs. One of the fun things about cdnjs is that they only have about 4 paragraphs of text and even so, their advice to use protocol relative URLs for resources taught me another useful trick.

We are also using Twitter Bootstrap 2.0 and Kickstrap to build the UI. My only gripe with Bootstrap is that you end up adding non-semantic CSS classes like 'span3'.  LIke any big complex library , bootstrap has a learning curve.  But with some help at stackoverflow, I was able to get past most of my issues.

From a coding standpoint, the site is basically built from Atom Feeds from Some Other Host's Content; news = Blogger posts and the home page and galleries are feeds from Picasa, at least for now.  I have both client-side Ajax and a server-side web hook to get Blogger content; this was more to force me to use both techniques.  Given how both Heroku and tumblr are on EC2, it may improve performance to use tumblr/imgur rather that Blogger/Picasa; its pretty hard to beat the latency of same datacenter.