<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mobile Browser Concurrency Test</title>
	<atom:link href="http://www.cloudfour.com/mobile-browser-concurrency-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cloudfour.com/mobile-browser-concurrency-test/</link>
	<description>Expert Web and Mobile Design, Development and Strategy</description>
	<lastBuildDate>Mon, 01 Mar 2010 02:56:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jermaine</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-11984</link>
		<dc:creator>Jermaine</dc:creator>
		<pubDate>Sun, 14 Feb 2010 00:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-11984</guid>
		<description>That is a impressive test not to mention the downtime in loading images one at a time. In seeing them work compatible with all browsers I bet is an awesome sight to see. </description>
		<content:encoded><![CDATA[<p>That is a impressive test not to mention the downtime in loading images one at a time. In seeing them work compatible with all browsers I bet is an awesome sight to see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-4842</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 05 May 2009 10:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-4842</guid>
		<description>Good site.I like it.

In today&#039;s world you have a number of choices to make: what device should your application use, what operating system, what networks will be relied on? And the list only keeps growing. Why not make things simpler?

Mobiquest′s Mobile Test Centre offers mobile application and testing services to simplify the testing needs of applications developers, service providers and handset manufacturers.</description>
		<content:encoded><![CDATA[<p>Good site.I like it.</p>
<p>In today&#8217;s world you have a number of choices to make: what device should your application use, what operating system, what networks will be relied on? And the list only keeps growing. Why not make things simpler?</p>
<p>Mobiquest′s Mobile Test Centre offers mobile application and testing services to simplify the testing needs of applications developers, service providers and handset manufacturers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Zorz</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-221</link>
		<dc:creator>Mario Zorz</dc:creator>
		<pubDate>Tue, 05 Aug 2008 22:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-221</guid>
		<description>Hi Jason, 

I wonder what results are you expecting from the actual majority of handsets. As you must already know, most mobile traffic happens to be handled by the wap gateway in the operator. So basically what you see on your servers (where your test pages are hosted) is the behavior that the wap gateway has about fetching URLs in a page, not the actual phone&#039;s. Let&#039;s assume a phone normal browser does open several concurrent connections, all of them will hit the wap gateway, who will consider doing whatever is best for handling overall traffic - not just this specific phone&#039;s requests. So the point is, the actual phone&#039;s bejavior is obscured by the existence of a wap gateway in the middle. Felt the need to clarify this, wap gateway and proxies to a minor extent is IMHO a major short-comming for this kind of tests. It will only work with smartphones and networks that allow phones to reach the internet directly, rather than actually normal networks (every operator has a wap gateway and most traffic is handled by such network element). 
Please kindly reply, I&#039;m intrigued. marionetazorz at yahoo dot com.</description>
		<content:encoded><![CDATA[<p>Hi Jason, </p>
<p>I wonder what results are you expecting from the actual majority of handsets. As you must already know, most mobile traffic happens to be handled by the wap gateway in the operator. So basically what you see on your servers (where your test pages are hosted) is the behavior that the wap gateway has about fetching URLs in a page, not the actual phone&#8217;s. Let&#8217;s assume a phone normal browser does open several concurrent connections, all of them will hit the wap gateway, who will consider doing whatever is best for handling overall traffic &#8211; not just this specific phone&#8217;s requests. So the point is, the actual phone&#8217;s bejavior is obscured by the existence of a wap gateway in the middle. Felt the need to clarify this, wap gateway and proxies to a minor extent is IMHO a major short-comming for this kind of tests. It will only work with smartphones and networks that allow phones to reach the internet directly, rather than actually normal networks (every operator has a wap gateway and most traffic is handled by such network element).<br />
Please kindly reply, I&#8217;m intrigued. marionetazorz at yahoo dot com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Going Fast on the Mobile Web : Cloud Four</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-127</link>
		<dc:creator>Going Fast on the Mobile Web : Cloud Four</dc:creator>
		<pubDate>Thu, 05 Jun 2008 07:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-127</guid>
		<description>[...] entitled Going Fast on the Mobile Web. Included in the presentation is the first results from our Mobile Browser concurrency test and some of the conclusions we&#8217;ve been drawing from the test [...]</description>
		<content:encoded><![CDATA[<p>[...] entitled Going Fast on the Mobile Web. Included in the presentation is the first results from our Mobile Browser concurrency test and some of the conclusions we&#8217;ve been drawing from the test [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gaylord aulke</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-114</link>
		<dc:creator>gaylord aulke</dc:creator>
		<pubDate>Tue, 27 May 2008 09:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-114</guid>
		<description>didnt see any images on my p1i but hope the results are still usable. cool initiative. looking forward to see the results.</description>
		<content:encoded><![CDATA[<p>didnt see any images on my p1i but hope the results are still usable. cool initiative. looking forward to see the results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mobile Speed Presentation at Web Visions : Cloud Four</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-105</link>
		<dc:creator>Mobile Speed Presentation at Web Visions : Cloud Four</dc:creator>
		<pubDate>Mon, 19 May 2008 03:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-105</guid>
		<description>[...] Mobile Browser Concurrency Test  [...]</description>
		<content:encoded><![CDATA[<p>[...] Mobile Browser Concurrency Test  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajax Performance &#187; Crowd sourcing mobile browser technical details</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-79</link>
		<dc:creator>Ajax Performance &#187; Crowd sourcing mobile browser technical details</dc:creator>
		<pubDate>Thu, 01 May 2008 03:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-79</guid>
		<description>[...] why I was excited to see a post by Jason Grigsby of Cloud Four (via Ajaxian) about a research project to collect this information with a clever server-side [...]</description>
		<content:encoded><![CDATA[<p>[...] why I was excited to see a post by Jason Grigsby of Cloud Four (via Ajaxian) about a research project to collect this information with a clever server-side [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <img src='http://www.cloudfour.com/wp-content/plugins/rpx/images/openid.png'/> Jason Grigsby</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-77</link>
		<dc:creator><img src='http://www.cloudfour.com/wp-content/plugins/rpx/images/openid.png'/> Jason Grigsby</dc:creator>
		<pubDate>Wed, 30 Apr 2008 17:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-77</guid>
		<description>Hi Michael,

Yes, the proxies are going to be challenging. We&#039;re actually looking for them in the apache logs. It was one of the notes we made in our methodology document about the potential short-comings of this way of testing.

So we recognize that as a problem and are going to try to correct for it when we analyze the data.

Thanks for testing and for the information on Japanese handsets.</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>Yes, the proxies are going to be challenging. We&#8217;re actually looking for them in the apache logs. It was one of the notes we made in our methodology document about the potential short-comings of this way of testing.</p>
<p>So we recognize that as a problem and are going to try to correct for it when we analyze the data.</p>
<p>Thanks for testing and for the information on Japanese handsets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlackBerry Browser Bug : Cloud Four</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-75</link>
		<dc:creator>BlackBerry Browser Bug : Cloud Four</dc:creator>
		<pubDate>Wed, 30 Apr 2008 13:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-75</guid>
		<description>[...] Mobile Browser Concurrency Test  [...]</description>
		<content:encoded><![CDATA[<p>[...] Mobile Browser Concurrency Test  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael(tm) Smith</title>
		<link>http://www.cloudfour.com/mobile-browser-concurrency-test/comment-page-1/#comment-73</link>
		<dc:creator>Michael(tm) Smith</dc:creator>
		<pubDate>Wed, 30 Apr 2008 05:49:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/36/mobile-browser-concurrency-test/#comment-73</guid>
		<description>I suspect you are going to find (if you haven&#039;t already) that this method is not going to be usable in some carrier networks  because the browsers on devices in those networks rely in part on proxies operated by the carriers -- and specifically, on proxies that do certain kinds of image manipulation.

I live in Japan and the KDDI/Au handset I use here has two browsers on it: One is a version of Opera 8.6, and the other is v6 of the Openwave browser. Both of them rely on proxies, and I think the same is true for preinstalled browsers on handsets for other carriers here (DoCoMo, Softbank, and Willcom).</description>
		<content:encoded><![CDATA[<p>I suspect you are going to find (if you haven&#8217;t already) that this method is not going to be usable in some carrier networks  because the browsers on devices in those networks rely in part on proxies operated by the carriers &#8212; and specifically, on proxies that do certain kinds of image manipulation.</p>
<p>I live in Japan and the KDDI/Au handset I use here has two browsers on it: One is a version of Opera 8.6, and the other is v6 of the Openwave browser. Both of them rely on proxies, and I think the same is true for preinstalled browsers on handsets for other carriers here (DoCoMo, Softbank, and Willcom).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
