Ask a Question related to Macromedia Flash Data Integration, Design and Development.
-
Lujunq #1
Socket access policy under Vista
Hi, for a long time I could easily make socket connections from my swf files
tom simples java servers on various ports (swfs embeded from activex, for
example). I used the simple python server policy file provided at this article
to open the needed tcp ports to my flash applications.
[url]http://www.adobe.com/devnet/flashplayer/articles/socket_policy_files.html[/url]
This works ok on Windows XP machines, Flash player 9 or 10. However, no single
Vista machine seems able to find the 843 port to load the policy file. I tried
to use another server for the policy file, tried to use another port for the
policy (Security.loadPolicyFile("xmlsocket://localhost:8008");) but nothing
seems to work - I just can't make my flash applications connect on Windows
Vista.
Is this a known problem? What am I doing wrong?
Thank you!
Lujunq Guest
-
Xml Socket policy to connect to a range of IPS
Dear, I have a problem with connecting to other servers rather the one who has served the swf file. i was facing the problem even on the same... -
Default user access rights in Vista
I've had four people using Vista beta test my software and all three have reported problems related to not being able to write to the application... -
Group policy for Vista
Has Microsoft released the group policy settings for Vista? Thanks -
authentication and access control (.NET socket connection)
Hi, Can someone point me in the right direction on a really simple access control issue? Here is the situation: 1. an app on a client... -
#25693 [NEW]: No access to posted variables via socket connection
From: a dot erler at brain-at-work dot de Operating system: Debian PHP version: 4.3.1 PHP Bug Type: Sockets related Bug... -
zazzo9 #2
Re: Socket access policy under Vista
I ran into a problem connecting to localhost in air on Vista -- apparently
Vista maps "localhost" to the ipv6 address "::1" which AIR does not understand.
Connecting directly to "127.0.0.1" instead of "localhost" resolved things for
me.
zazzo9 Guest



Reply With Quote

