PUBLIC MARKS with tags network & apache

What is Shindig? Shindig is a container for hosting social application consisting of four parts: * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API. * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript. * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore). * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends. Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes: * Profiles * Relationships * Activities * Shared applications * Authentication * Authorization

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

Typical Scenario: You have a web server that serves your domain. You write a simple script to restart apache each night and pipe the logs off to your analyzer. It works. ISP/Hosting Scenario: Each server hosts many domains. You may also have load balanced servers (multiple machines) serving each domain. A tool like this is necessary to: 1. collect all the log files from each server 2. split the logs based on the virtual host(s) 3. discard invalid entries (phishing, referrer spam, etc) 4. sort them into chronological order 5. feed logs into analyzer 6. do something with the raw logs (compress, save to vhost dir, etc) [edit]

Globule is a third-party module for the Apache Web server that allows a given server to replicate its documents to other Globule servers. It takes care of maintaining consistency between the replicas, of monitoring the servers, and of automatically redirecting clients to one of the available replicas. Globule also supports the replication of PHP documents. It runs on Unix and Windows systems.