THE VIEW -- Writing Efficient, Effective Web Code for Domino, Part 7: The Final Chapter

In the course of this series, I’ve introduced Domino Web development techniques that should be applicable in just about every environment and situation. Now, in the final installment, I share some techniques that may give you a performance increase depending on your situation:

Selecting the right image format to achieve the best results with the smallest possible footprint.
Eliminating unnecessary data in your HTTP requests.
Splitting content across domains to avoid hitting the limit on simultaneous downloads of multiple files.
Using inline code dynamically. For a first-time visitor, the page loads in the browser with inline JavaScript and CSS styles, and the external libraries are placed in the browser cache in the background. The next time that user returns, the cached external files are used instead of the inline code to provide further performance improvement.
Performing dynamic migration of external files by enabling the Domino server to migrate multiple JavaScript libraries for you on request. This technique is handy if you need to use multiple external files — for example, to maintain the code more efficiently in several smaller libraries rather than in one big library.

I also have a few parting gifts for you:

A technique for making your Web code look great in Domino Designer and getting color-coded code directly on your page or form
A cool way to replace static image headers using scalable Inman Flash Replacement (sIFR), including a code example in the download database that you can use on your own pages

Note!

You can follow along with the examples in the Domino database labb1_Part7.nsf accompanying this article. I have tested this database in Domino versions 7 through 8, and it should work in version 6 as well.

The page examples in the download database work in Firefox 2 and 3, Internet Explorer 6, 7, and 8, Opera 9.5, and Safari 4.03.

As in my previous articles, I use Aptana Studio as the Web editor.