Because the new security policy for the socket connections have eaten up days of my prime years here’s a collection of resources that I found useful. My specific problem occurred in the context of using Electroserver 4.05 so I’ll document the relevant details as they come up as well. This post serves more as a document of what I have tried to keep me from repeating myself and as a sanity check. Hopefully it’ll be helpful to others on the same rocky road.
- Kira’s Web Toolbox- Setting up A Flash Policy File- this actually explained the 3 second delay we experienced when you first hit a socket server. Also includes a perl socket server that listens on 843 and returns a global policy file
- Adobe.com Understanding Flash 9 security updates
- Policy File Changes in Player 9 and 10
- How to log policy file results for debugging so you don’t lose your entire mind.
- Reassurance from adobe’s Jira that this is not a bug – then again I’ve read a link that pointed out that if the server does not find a file on port 843 it fails to look for it elsewhere despite the statement in the debug log that this should not be a problem
- The behavior is similar to what is described here as a Flash Palyer bug
Resources
- Use FlashTracer for remote debugging
I’ll add more in the coming days as I work through this.
Related posts:
- Flex Profiler is not yet a friend of Mine. I spent a
- IBM Tool For Flash/Flex Vulnerability Discovery Just came
- Zend AMF Misadventures- Pitfalls and Tips Update 1/1
- links for 2009-05-01 Technora
- Two ways to set of mod_rewrite You can ei
Related posts brought to you by Yet Another Related Posts Plugin.
Bedeviled