Prism is a simple XULRunner-based browser that hosts web applications without the normal web browser user interface. Prism is based on a concept called Site-Specific Browsers (SSB).

The first time you hear about site-specific browsing, you raise a brow and wonder. What is this thing? And how is it different from the ... eh ... regular browsing.

Prism , Single-serving Browser for Web Application from Mozilla

Mozilla Labs recently released the 1.0 beta of Prism. Prism is a XULRunner-based browser designed to run Web applications. It is not a standalone web browser, It will run your web applications like gmail, googledocs smoothly.

"A new piece of software has come to my attention today, a Mozilla project called WebRunner that aims to provide an easy way to create site-specific browsers (SSBs). The project is basically an extension on the XULRunner software, which itself is standalone version of the XUL engine that underpins the big Mozilla projects (Firefox, Thunderbird, Sunbird, Seamonkey)..."

WebRunner, at version 0.5 now, is a stripped-down version of Firefox that allows you to run a single site at a time in its own process. The browser has a minimal user interface with no toolbars or navigation UI -- just a window with the bare minimum needed to use applications like Google Reader, Flickr, Web-based help desks, or any Webmail client.

Continuing with the KDE 4.4 theme we will turn our phasers towards configuring window-specific options. What exactly does this mean? It means you can configure options for a specific window that apply only to a specific window or a specific application.

For web browsing, most of us would prefer Firefox or Opera because of their speed, security, stability, and overall features. While a handful of people may like surfing the web with some of those terminal-based browsers. For a change, why not try some web browsers that would perhaps cater to a few of your specific needs and would serve as an alternative to your existing browser.

Web developers know the importance of testing web sites and blogs on the different web browsers available. A site/blog can look great on one browser, but if you try to access it on another one, it can probably look garbled. It’s a hassle checking a web site/blog on Internet Explorer, Firefox, Chrome, Safari, Opera, etc.

This tutorial explains how you can configure Apache2 to set the Expires HTTP header and the max-age directive of the Cache-Control HTTP header of static files (such as images, CSS and Javascript files) to a date in the future so that these files will be cached by your visitors' browsers.