<?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: Keeping third party JavaScript from slowing down your site</title>
	<atom:link href="http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/</link>
	<description>A blog about killer code</description>
	<pubDate>Thu, 04 Dec 2008 21:16:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Chris Blow</title>
		<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/#comment-190</link>
		<dc:creator>Chris Blow</dc:creator>
		<pubDate>Mon, 02 Jun 2008 06:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=29#comment-190</guid>
		<description>@joey: the js is dynamically written from the server, so you need a "live" connection to the third party. 

But WRT the security issue, you are right on to raise the issue: it was just a few months ago that perl.com was hacked because one of their ad partners (read: remote js) had their domain name expire! ....

When was the last time you checked your 
"content partner's" registration expiry? :)</description>
		<content:encoded><![CDATA[<p>@joey: the js is dynamically written from the server, so you need a &#8220;live&#8221; connection to the third party. </p>
<p>But WRT the security issue, you are right on to raise the issue: it was just a few months ago that perl.com was hacked because one of their ad partners (read: remote js) had their domain name expire! &#8230;.</p>
<p>When was the last time you checked your<br />
&#8220;content partner&#8217;s&#8221; registration expiry? :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joey Mazzarelli</title>
		<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/#comment-189</link>
		<dc:creator>Joey Mazzarelli</dc:creator>
		<pubDate>Sun, 01 Jun 2008 22:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=29#comment-189</guid>
		<description>Have you considered the security aspect of directly including 3rd-party scripts? You are effectively giving them the ability to steal cookies, alter the behavior of your site, read user data, etc.

It requires little effort to make a local copy of the script and use that one instead. And you don't have to worry bad behavior (malicious or accidental) nor updates breaking your site.

Just a thought.</description>
		<content:encoded><![CDATA[<p>Have you considered the security aspect of directly including 3rd-party scripts? You are effectively giving them the ability to steal cookies, alter the behavior of your site, read user data, etc.</p>
<p>It requires little effort to make a local copy of the script and use that one instead. And you don&#8217;t have to worry bad behavior (malicious or accidental) nor updates breaking your site.</p>
<p>Just a thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Michaux</title>
		<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/#comment-187</link>
		<dc:creator>Peter Michaux</dc:creator>
		<pubDate>Sat, 31 May 2008 21:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=29#comment-187</guid>
		<description>I don't think using a central source for common JavaScript libraries is such a great idea. At least not in all cases. I don't think I would use such a source.

http://peter.michaux.ca/article/7906

These startups you mention don't want you to think about the possible costs. That would discourage adoption.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think using a central source for common JavaScript libraries is such a great idea. At least not in all cases. I don&#8217;t think I would use such a source.</p>
<p><a href="http://peter.michaux.ca/article/7906" rel="nofollow">http://peter.michaux.ca/article/7906</a></p>
<p>These startups you mention don&#8217;t want you to think about the possible costs. That would discourage adoption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaisen</title>
		<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/#comment-186</link>
		<dc:creator>jaisen</dc:creator>
		<pubDate>Sat, 31 May 2008 21:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=29#comment-186</guid>
		<description>@Peter, the google hosted js libs are a great idea.  Google's infrastructure is as reliable and fast as you can expect from a third party.

My main concern is that startups while providing great services don't have infrastructure that's as reliable as one might expect.  So if you *must* include their scripts it should become a standard practice to minimize your dependency on them.

I would like for these startups to address this issue instead of just giving you a script tag to paste into your site without thinking of the possible cost.</description>
		<content:encoded><![CDATA[<p>@Peter, the google hosted js libs are a great idea.  Google&#8217;s infrastructure is as reliable and fast as you can expect from a third party.</p>
<p>My main concern is that startups while providing great services don&#8217;t have infrastructure that&#8217;s as reliable as one might expect.  So if you *must* include their scripts it should become a standard practice to minimize your dependency on them.</p>
<p>I would like for these startups to address this issue instead of just giving you a script tag to paste into your site without thinking of the possible cost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Michaux</title>
		<link>http://www.jaisenmathai.com/blog/2008/05/31/keeping-third-party-javascript-from-slowing-down-your-site/#comment-185</link>
		<dc:creator>Peter Michaux</dc:creator>
		<pubDate>Sat, 31 May 2008 21:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.jaisenmathai.com/blog/?p=29#comment-185</guid>
		<description>You could use this technique even for your own JavaScript files. Some people do.

There may be a trend to start using more JavaScript files from third-party servers.

http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax-apps-with-googles-infrastructure

I think the JavaScript files in mashups slow things down because there is database interaction to dynamically generate that JavaScript. The part that the JavaScript is from another server is probably not what makes the page painfully slow to finish loading. It may make it slower however as extra connections need to be made.</description>
		<content:encoded><![CDATA[<p>You could use this technique even for your own JavaScript files. Some people do.</p>
<p>There may be a trend to start using more JavaScript files from third-party servers.</p>
<p><a href="http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax-apps-with-googles-infrastructure" rel="nofollow">http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax-apps-with-googles-infrastructure</a></p>
<p>I think the JavaScript files in mashups slow things down because there is database interaction to dynamically generate that JavaScript. The part that the JavaScript is from another server is probably not what makes the page painfully slow to finish loading. It may make it slower however as extra connections need to be made.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
