<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: What is a page? Part 2</title>
	<atom:link href="http://www.ajaxperformance.com/2006/10/28/what-is-a-page-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ajaxperformance.com/2006/10/28/what-is-a-page-part-2/</link>
	<description>A blog by Ryan Breen of Gomez</description>
	<pubDate>Mon, 01 Dec 2008 22:51:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Ajax Performance &#187; What is a page? Part 3</title>
		<link>http://www.ajaxperformance.com/2006/10/28/what-is-a-page-part-2/#comment-46</link>
		<dc:creator>Ajax Performance &#187; What is a page? Part 3</dc:creator>
		<pubDate>Tue, 14 Nov 2006 15:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxperformance.com/?p=18#comment-46</guid>
		<description>[...] Active measurement of web application performance involves simulating a real end user hitting a series of pages of the application and performing some action to move from one step to the next. An example transaction may start with a user loading up www.ebay.com, searching for &#8216;Beanie Babies&#8217;, and clicking the first result of the Beanie Baby search. That transaction would be 3 steps &#8212; home page, search results, and listing for the first search item. Organizations who perform this type of testing on their production applications have developed an understanding for how long each step should take and use this expectation to benchmark their product over time. This is the page-by-page model I discussed in Part 2. [...]</description>
		<content:encoded><![CDATA[<p>[...] Active measurement of web application performance involves simulating a real end user hitting a series of pages of the application and performing some action to move from one step to the next. An example transaction may start with a user loading up <a href="http://www.ebay.com" rel="nofollow">http://www.ebay.com</a>, searching for &#8216;Beanie Babies&#8217;, and clicking the first result of the Beanie Baby search. That transaction would be 3 steps &#8212; home page, search results, and listing for the first search item. Organizations who perform this type of testing on their production applications have developed an understanding for how long each step should take and use this expectation to benchmark their product over time. This is the page-by-page model I discussed in Part 2. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajax Performance &#187; Oops, make that 4 seconds</title>
		<link>http://www.ajaxperformance.com/2006/10/28/what-is-a-page-part-2/#comment-44</link>
		<dc:creator>Ajax Performance &#187; Oops, make that 4 seconds</dc:creator>
		<pubDate>Sun, 12 Nov 2006 21:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxperformance.com/?p=18#comment-44</guid>
		<description>[...] Looks like my algorithm for calculating user-acceptable latency needs to be updated. Akamai says it&#8217;s now 4 seconds, at least for retail sites. [...]</description>
		<content:encoded><![CDATA[<p>[...] Looks like my algorithm for calculating user-acceptable latency needs to be updated. Akamai says it&#8217;s now 4 seconds, at least for retail sites. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.528 seconds -->
