<?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: ExternalInterface bug can mangle data from JavaScript</title>
	<atom:link href="http://joshblog.net/2007/12/16/flash-player-9-external-interface-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://joshblog.net/2007/12/16/flash-player-9-external-interface-bug/</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Wed, 16 May 2012 17:12:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Marlin</title>
		<link>http://joshblog.net/2007/12/16/flash-player-9-external-interface-bug/#comment-1546</link>
		<dc:creator>Marlin</dc:creator>
		<pubDate>Mon, 02 Mar 2009 22:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeuslabs.us/2007/12/16/flash-player-9-external-interface-bug/#comment-1546</guid>
		<description>I realize this is more than two years old, but this blog is also indexed by Google and no doubt comes up from time to time.

The bug you have noted where &lt;![CDATA[ is not handled correctly has been described by Brad Newberg here:

http://codinginparadise.org/weblog/2006/02/how-to-speed-up-flash-8s.html

Here is Brad&#039;s explanation:
I found all of the JavaScript serialization methods in the Flash player (and they are in JavaScript) by using the Microsoft Debugger (they all live on window.parent; you&#039;ll see them appear a few seconds after the Flash player loads). These methods handle all of the serialization and deserialization and all begin with the name __flash__. It turns out that they ARE using XML internally, and did not implement a real XML parser on the C++/Flash side which can correctly handle CDATA sections. They are also doing evals(), which is one of the reasons it is slow.</description>
		<content:encoded><![CDATA[<p>I realize this is more than two years old, but this blog is also indexed by Google and no doubt comes up from time to time.</p>
<p>The bug you have noted where &lt;![CDATA[ is not handled correctly has been described by Brad Newberg here:</p>
<p><a href="http://codinginparadise.org/weblog/2006/02/how-to-speed-up-flash-8s.html" rel="nofollow">http://codinginparadise.org/weblog/2006/02/how-to-speed-up-flash-8s.html</a></p>
<p>Here is Brad&#8217;s explanation:<br />
I found all of the JavaScript serialization methods in the Flash player (and they are in JavaScript) by using the Microsoft Debugger (they all live on window.parent; you&#8217;ll see them appear a few seconds after the Flash player loads). These methods handle all of the serialization and deserialization and all begin with the name __flash__. It turns out that they ARE using XML internally, and did not implement a real XML parser on the C++/Flash side which can correctly handle CDATA sections. They are also doing evals(), which is one of the reasons it is slow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caryl</title>
		<link>http://joshblog.net/2007/12/16/flash-player-9-external-interface-bug/#comment-1545</link>
		<dc:creator>caryl</dc:creator>
		<pubDate>Fri, 12 Sep 2008 19:08:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeuslabs.us/2007/12/16/flash-player-9-external-interface-bug/#comment-1545</guid>
		<description>Good 235rter2rwer23r</description>
		<content:encoded><![CDATA[<p>Good 235rter2rwer23r</p>
]]></content:encoded>
	</item>
</channel>
</rss>

