<?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: Be careful with the new Flash Player 9.0.115.0 security changes.</title>
	<atom:link href="http://www.arpitonline.com/blog/2008/01/13/be-careful-with-the-new-flash-player-901150-security-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.arpitonline.com/blog/2008/01/13/be-careful-with-the-new-flash-player-901150-security-changes/</link>
	<description>"I write pretty software"</description>
	<lastBuildDate>Mon, 26 Jul 2010 08:34:18 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: edd@epic.co.uk</title>
		<link>http://www.arpitonline.com/blog/2008/01/13/be-careful-with-the-new-flash-player-901150-security-changes/comment-page-1/#comment-25562</link>
		<dc:creator>edd@epic.co.uk</dc:creator>
		<pubDate>Mon, 14 Jan 2008 09:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.arpitonline.com/blog/?p=106#comment-25562</guid>
		<description>thanks for posting this.

we found something similar last week to do with communicating between flash movies and javascript when running an application locally, in development for example.

normally we can overcome these security settings by always allowing access in the global.security.settings however it seems that running the app over http is the only way for now for the kind of communication our applications require.

great resources on the issue though, thanks a lot.</description>
		<content:encoded><![CDATA[<p>thanks for posting this.</p>
<p>we found something similar last week to do with communicating between flash movies and javascript when running an application locally, in development for example.</p>
<p>normally we can overcome these security settings by always allowing access in the global.security.settings however it seems that running the app over http is the only way for now for the kind of communication our applications require.</p>
<p>great resources on the issue though, thanks a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
