PUBLIC MARKS with tags apache & cache

Comparatif des fichiers de configuration

Le fonctionnement du mode cache apache en HTTP/1.1

Vous avez développé votre tout dernier web service destinés à être utilisé par 2 ou 3 autres équipes en interne (voire en externe par des partenaires). Il (le web service) fonctionne bien, tellement bien, que vous commencez à avoir plusieurs dizaines de requêtes par jour. Vous n'aviez pas forcément optimisé les performances du web service, les temps de réponses ne sont pas au beau fixe car vous chargez 150 classes PHP qui sont nécessaires au tout dernier framework à la mode pour accéder à une table de base de données et faire une requête select sur un champ avec une clé primaire pour retourner la fiche descriptive d'un utilisateur, d'un partenaire ou d'un produit. Ou bien, pire encore, pour renvoyez votre catalogue de produits qui fait 150Ko une fois transformé au format XML.

A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses — like HTML pages, images and files (collectively known as representations) — for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again.

Caching is a great example of the ubiquitous time-space tradeoff in programming. You can save time by using space to store results. In the case of websites, the browser can save a copy of images, stylesheets, javascript or the entire page. The next time the user needs that resource (such as a script or logo that appears on every page), the browser doesn’t have to download it again. Fewer downloads means a faster, happier site.

Vey useful links for cache control and browser behaviors * Explain of cache control in detail (very nice article! ) http://betterexplained.com/articles/how-to-optimize-your-site-with-http-caching/ * The State of Browser Caching: http://www.mnot.net/blog/2006/05/11/browser_caching * XMLHttpRequest caching: http://www.mnot.net/javascript/xmlhttprequest/cache.html

Caching is the temporary storage of frequently accessed data in higher speed media (typically SRAM or RAM) for more efficient retrieval. Web caching stores frequently used objects closer to the client through browser, proxy, or server caches. By storing "fresh" objects closer to your users, you avoid round trips to the origin server, reducing bandwidth consumption, server load, and most importantly, latency. This article shows how to configure your Apache server for more efficient caching to save bandwidth and improve performance. Caching is not just for static sites, even dynamic sites can benefit from caching. Graphics and multimedia typically don't change as frequently as (X)HTML files. Graphics that seldom change like logos, headers, and navigation can be given longer expiration times while resources that change more frequently like XHTML and XML files can be given shorter expiration times. By designing your site with caching in mind, you can target different classes of resources to give them different expiration times with only a few lines of code.

Caching is the temporary storage of frequently accessed data in higher speed media (typically SRAM or RAM) for more efficient retrieval. Web caching stores frequently used objects closer to the client through browser, proxy, or server caches. By storing "fresh" objects closer to your users, you avoid round trips to the origin server, reducing bandwidth consumption, server load, and most importantly, latency. This article shows how to configure your Apache server for more efficient caching to save bandwidth and improve performance. Caching is not just for static sites, even dynamic sites can benefit from caching. Graphics and multimedia typically don't change as frequently as (X)HTML files. Graphics that seldom change like logos, headers, and navigation can be given longer expiration times while resources that change more frequently like XHTML and XML files can be given shorter expiration times. By designing your site with caching in mind, you can target different classes of resources to give them different expiration times with only a few lines of code.

This article shows 2 awesome ways to implement caching on your website using Apache .htaccess (httpd.conf) files on the Apache Web Server. Both methods are extremely simple to set up and will dramatically speed up your site!

Apache Synapse offers a wide range of connectivity, including HTTP/S, JMS, (S)FTP, SOAP, WS-ReliableMessaging and WS-Security. The project has been designed to allow administrators to support advanced functionality such as load-balancing, throttling, and failover without writing code. The new Apache Synapse 1.1 release includes many enhancements based on feedback from users, including * Apache VFS based file transport - supports File System, FTP, SFTP, JAR, ZIP, TAR, GZIP, Mime * Scheduled Task support makes it simple to run repetitive tasks * XQuery mediator - simplifies XML transformation with the XQuery standard * POJO Command mediator - allows the creation of message-independent mediation logic * DB Report and DB Lookup mediators - support message augmentation and database logging * Cache and Throttle mediators/enhancements - improve performance and manage load on existing services * Split/Clone/Aggregate mediators - support batch processing of large messages * Improved logging and tracing support With asynchronous support for HTTP and HTTPS, Apache Synapse has very high scalability under load, supporting thousands of concurrent connections even with limited threads. Combined with streaming XML support, Apache Synapse has class-leading performance results. The Apache Synapse code and binaries are available from the website at http://ws.apache.org/synapse

This article shows 2 awesome ways to implement caching on your website using Apache .htaccess (httpd.conf) files on the Apache Web Server. Both methods are extremely simple to set up and will dramatically speed up your site!

JBoss Application Server is the #1 most widely used Java application server on the market. A J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals, JBoss Application Server provides the full range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence.