{"id":434,"date":"2008-06-27T18:57:59","date_gmt":"2008-06-27T17:57:59","guid":{"rendered":"http:\/\/wp.devco.net\/?p=434"},"modified":"2009-10-09T13:59:27","modified_gmt":"2009-10-09T12:59:27","slug":"flashpolicyd_20","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2008\/06\/27\/flashpolicyd_20.php","title":{"rendered":"flashpolicyd 2.0"},"content":{"rendered":"

I wrote a multi threaded server for Adobe Flash Policy<\/a> requests, some background from Adobe:<\/p>\n

Since policy files were first introduced, Flash Player has
\nrecognized \/crossdomain.xml<\/kbd> as a master location for URL policy files. However, prior to version 9,0,115,0,
\nFlash Player did not recognize a fixed master location for socket policy files.
\nFlash Player 9,0,115,0 introduces a concept of socket master policy files<\/em>,
\nwhich are served from the fixed TCP port number 843. <\/p><\/blockquote>\n

If your application currently requires \/crossdomain.xml<\/i> files to work properly while making Socket requests you should pay close attention to this, as of the current latest version of Flash Player your application will STOP<\/b> working if you do not run a policy server.  You need to read this link<\/a> and take appropriate action.<\/p>\n

The servers that Adobe provides are not full featured so I set out to write one, the resulting server can be found on my wiki at http:\/\/www.devco.net\/pubwiki\/FlashPolicyd<\/a> I will regularly post updates here.<\/p>\n

A quick feature list:<\/p>\n