<?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 1</title>
	<atom:link href="http://www.ajaxperformance.com/2006/10/10/what-is-a-page-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ajaxperformance.com/2006/10/10/what-is-a-page-part-1/</link>
	<description>A blog by Ryan Breen of Gomez</description>
	<pubDate>Mon, 01 Dec 2008 22:23:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Ajax Performance &#187; If you are reading this post, you are contributing to a benchmark</title>
		<link>http://www.ajaxperformance.com/2006/10/10/what-is-a-page-part-1/#comment-52</link>
		<dc:creator>Ajax Performance &#187; If you are reading this post, you are contributing to a benchmark</dc:creator>
		<pubDate>Mon, 20 Nov 2006 02:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxperformance.com/?p=9#comment-52</guid>
		<description>[...] In several earlier posts, I talked about the increasing migration of complexity to the edges of the network, to within the web browser. Today, tools to manage and understand that complexity and how it relates to real user experience don&#8217;t really exist, and that&#8217;s a problem we have been thinking about for the past year or so. We realized that the best way to understand what is happening inside the end user&#8217;s browser is to be inside the end user&#8217;s browser, so we are building a JavaScript based technology, dubbed Actual Experience XF, which does just that. I previewed this approach during my presentation at the Ajax Experience, but now I&#8217;m finally allowed to demonstrate it publicly. [...]</description>
		<content:encoded><![CDATA[<p>[...] In several earlier posts, I talked about the increasing migration of complexity to the edges of the network, to within the web browser. Today, tools to manage and understand that complexity and how it relates to real user experience don&#8217;t really exist, and that&#8217;s a problem we have been thinking about for the past year or so. We realized that the best way to understand what is happening inside the end user&#8217;s browser is to be inside the end user&#8217;s browser, so we are building a JavaScript based technology, dubbed Actual Experience XF, which does just that. I previewed this approach during my presentation at the Ajax Experience, but now I&#8217;m finally allowed to demonstrate it publicly. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajax Performance &#187; Network Computing coverage of speedbumps in Ajax adoption</title>
		<link>http://www.ajaxperformance.com/2006/10/10/what-is-a-page-part-1/#comment-7</link>
		<dc:creator>Ajax Performance &#187; Network Computing coverage of speedbumps in Ajax adoption</dc:creator>
		<pubDate>Thu, 02 Nov 2006 00:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxperformance.com/?p=9#comment-7</guid>
		<description>[...] Most customers I&#8217;ve worked with run into exactly the issues listed in this article. Because we&#8217;re still in a very immature phase of adoption, Ajax is often introduced into applications without a lot of thought about manageability, performance, etc. I touched on this some in the first section of What is a page?, and it&#8217;s gratifying to see more discussion of this in the mainstream enterprise press. [...]</description>
		<content:encoded><![CDATA[<p>[...] Most customers I&#8217;ve worked with run into exactly the issues listed in this article. Because we&#8217;re still in a very immature phase of adoption, Ajax is often introduced into applications without a lot of thought about manageability, performance, etc. I touched on this some in the first section of What is a page?, and it&#8217;s gratifying to see more discussion of this in the mainstream enterprise press. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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