I would also include this article...
http://www.martijndevisser.com/blog/article/why-crossdomainxml-is-a-good-thing
It's gotta kewl flash slide show that explains it pretty well.
On 8/25/06, Ted
Patrick <[EMAIL PROTECTED]com
> wrote:
I will get that added ASAP. Great feedback.
Anyone else?
Ted Patrick
Flex Evangelist
Adobe Systems Incorporated
________________________________________
Subject: RE: [flexcoders] POP3 by Socket
Ted, that is a handy site.
A suggestion: An issue that is not obvious to those who are
not web/network administratiors is: "Where do I put the crossdomain.xml
file". While I bet this is discussed on more than one of the links
you provide, consider a quick paragraph on the subject, for additional
convenience.
The usual response: "In the root of the web server" is
not enough for non-experts. Include an example path for, say the default
integrated Flex 1.5 install, one for a default Tomcat install, and one for a
default IIS install.
I figured mine out by putting a full access crossdomain file in
every possible folder until my call worked, then deleting them until I
broke it again. This showed me the right place. You see why I am
not offering to provide the examples!
Tracy
________________________________________
From: [EMAIL PROTECTED]ups.com [mailto: [EMAIL PROTECTED]ups.com]
On Behalf Of Ted Patrick
Sent: Friday, August 25, 2006 12:14 PM
To: [EMAIL PROTECTED]ups.com
Subject: RE: [flexcoders] POP3 by Socket
Rogerio,
http://www.crossdomainxml.org
http://www.crossdomainxml.org
With Socket operations you will need to have a crossdomain.xml
file on the server you are connecting to, in this case the POP server! This
particular crossdomain.xml file needs to permit access to use low/high
ports for inbound connections. It is identical to the process needed to support
XMLSocket servers.
The use of crossdomain policy files prevents Flash/Flex clients
from abusing other peoples servers. As permission is delegated to the server
owner, they can decide what ports Flash Player can connect to.
Example:
<cross-domain-policy>
<allow-access-from domain="*"
to-ports="507" />
<allow-access-from domain="*.foo.com"
to-ports="507,516" />
<allow-access-from domain="*.bar.com"
to-ports="516-523" />
<allow-access-from domain="www.foo.com"
to-ports="507,516-523" />
<allow-access-from domain="www.bar.com" to-ports="*"
/>
</cross-domain-policy>
I put together this small site on crossdomain policy files. It
doesn't have any glits and gives you the bare bones knowledge on using
crossdomain.
http://www.crossdomainxml.org
http://www.crossdomainxml.org
IFBIN on Flexcoders!!!!
You just made my day!
Go IFBIN!
Cheers,
Ted Patrick
Flex Evangelist
Adobe Systems Incorporated
________________________________________
From: [EMAIL PROTECTED]ups.com [mailto: [EMAIL PROTECTED]ups.com]
On Behalf Of Santo
Sent: Friday, August 25, 2006 6:46 AM
To: [EMAIL PROTECTED]ups.com
Subject: [flexcoders] POP3 by Socket
Bom dia pessoal,
Hi folks,
I want to know if anyone of you try make the POP3 by Socket
example,
from IFBIN(Flex by Example), work with final version of Flex 2.
Now that he´s free, I try to test something but it just don´t
work.
Don´t give me any errors. Seems to be a security issue, like
crossdomain, but I can´t figure out the real problem.
Thanks
Rogerio Gonzalez
