View Single Post
  #4 (permalink)  
Old 01-08-2009
xdm xdm is offline
Registered User
 
Name: Jose Gutierrez de la Concha
Organization: personal
Project: No Yet
 
Join Date: Sep 2003
Location: La Coruņa, Spain
Posts: 401
Hi Joost,

You are right the requisites are incorrect , Silverlight required that the policyserver listen on the target site. in that case the Glacier2 adddress.

We should fix this requisites in IceSl and ChatDemo releases thanks for pointed this.

Quote:
If the connection request was from sockets to the site (cross-domain or site of origin), the Silverlight 2 runtime tries to open a connection using TCP to a well-known port (port 943) on the target site. If a TCP connection can be established, the Silverlight 2 runtime sends the special string <policy-file-request/> to the server to request a Silverlight policy file. The Silverlight 2 runtime then waits to receive a reply from the target site that contains a Silverlight policy file. If this Silverlight policy file is returned (even if there is an error in parsing the file), it is used as the policy file for that socket request and all subsequent requests to that target site for the entire session of the Silverlight application.
From Silverlight 2 doc Network Security Access Restrictions in Silverlight 2
Reply With Quote