Monthly Archives: January 2009


Making Your DHTML or AJAX Application Bookmarkable

As more and more websites are embracing “web 2.0” standards and evolving into more responsive dynamic applications many of them are losing basic functionality such as bookmark-ability.

In order to present a richer interface or to reduce page load times and improve responsiveness it can be […]

By | January 28th, 2009|ATG|4 Comments

Additional CDN Information

A few popular commercial CDN services are:

End user performance is typically increased roughly 20-25% by the addition of a good CDN solution. This does not count the reduced capacity requirements of your server farm, which is an added […]

By | January 23rd, 2009|ATG|0 Comments Security Breach

The job board database was illegally accessed and large amounts of user data were stolen.


As is the case with many companies that maintain large databases of information, Monster is the target of illegal attempts to access and extract information from its database. […]

By | January 23rd, 2009|ATG, Security|2 Comments

Improving ATG Performance With a CDN

Why use a CDN?

A Content Delivery Network, or CDN, is essentially a system of geographically distributed web servers which serve static content, typically images, video, and other bandwidth intensive files. This serves two purposes: it keeps your servers from having to handle those requests and it serves those files to the end user from […]

By | January 19th, 2009|ATG|1 Comment

Improving Secondary Asset Loading Time for an ATG Application

Now that we covered improving the performance of serving the HTML from the JSP, we need to tackle the bigger problem of all of the secondary assets and media that the page loads to display correctly. This includes images, Javascript, CSS, Flash, videos, etc…

The reason that these secondary page assets are so critical for page performance is two-fold. First, there are many more of them for each page than the single HTML file. This means more HTTP connections have to opened and closed, more files have to be transfered from the server to the user’s computer. This takes a lot of time. Second, most of these assets tend to be static, they don’t change very often. This means we can cache them.

Reduce the number of assets

The first thing we need to do is to try to reduce the number of secondary assets which need to be loaded. You can try to simplify the page design to require less assets, reduce the number of images used, replace images with text (which is more accessible and search engine friendly anyhow), etc… Also reducing large files like videos and Flash files can make a significant improvement on page load times. Personally, for things other than video players and similar things, I strongly dislike the use of Flash. There is an impressive amount of rich interface and interaction that can be created using DHTML and AJAX. It generally performs better, loads faster, and is easier to make search engine friendly.


By | January 17th, 2009|ATG|5 Comments