I'm trying to speed up my Twitter application, and one of the recommendations I ran across was to increase the download parallelization of the numerous Twitter profile images on my webpage.
Just out of curiosity, I tried: http://a1.twimg.com/profile_images/469603814/twitter20091011-2_bigger.jpg http://a2.twimg.com/profile_images/469603814/twitter20091011-2_bigger.jpg http://a3.twimg.com/profile_images/469603814/twitter20091011-2_bigger.jpg http://a4.twimg.com/profile_images/469603814/twitter20091011-2_bigger.jpg http://a5.twimg.com/profile_images/469603814/twitter20091011-2_bigger.jpg and noticed they all resolve. Perhaps Twitter is using this same performance tactic? Can we rely on spreading our profile image requests from a1.twimg.com to a5.twimg.com for our applications?
