Hi Alias, I've never fully understood the need for the crossdomain policy file. I think it was Sho who tried to explain it to me in a very technical manner but either I'm really thick (definite possibility) or I just don't get the value of something where you essentially need to disable the security via a crossdomain.xml file to get something like web services to work without the need of a proxy. It seems to me to be a artificial restriction aimed at selling more server licenses. It also is a major handicap for Flash when compared to Java and rules out the creation of a whole host of applications in Flash (like a POP3/IMAP email reader that can check email from any domain.) "Sure it'll work, just ask your ISP to put a crossdomain.xml file in their root... Ummm, what?"
All that said, I'm personally worried about the impact of several, incompatible, Flash player implementations and how that will affect the reputation of the Flash Platform. Currently, Flash is pretty much a write-once, run-anywhere platform and that's one of its (if not its greatest) unique selling point. (Maintaining state on the client was too, but "AJAX" apps can do that too now.) I'm worried that competing players will confuse developers and users alike. I'm even worried about the increasing rate of change in the release of Macromedia Players, especially the pre-release ones (8, followed a few months later by alpha 8.5, beta 8.5?, 8.5?, etc.) I believe that *stability* in the player is very important. Aral _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
