webScriptAccess

Question 1.
   During development it is not practical to serve my SOAP service from 
the same port as my script files that access it.  How am I able to 
configure mozilla to allow a script served on one port to access a 
service on another port.  I am running mozilla 1.8a6.

Question 2.
   Is the "New Security Model" proposal linked to from mozilla's web 
services page enabled in mozilla?  If so, wouldn't the following file 
named "web-scripts-access.xml" served from localhost on port 80 from the 
same directory as the scripts that are trying to access a service on 
port 9900 satisfy mozilla's new security model?  If the answer is "NO" 
because I haven't provided a corresponding <wsa:delegate> directive in a 
file named "web-scripts-access.xml" on port 9900, please refer to 
Question 1.  In other words, many soap implementations come with an http 
server builtin to aid in development, but one which can't easily be 
configured to serve anything other than the soap service.

<?xml version="1.0" encoding="UTF-8"?>
<wsa:webScriptAccess xmlns:wsa="http://www.mozilla.org/2002/soap/security">
<wsa:allow type="soap" from="http://localhost:9900"/>
<wsa:allow type="soapv" from="http://localhost:9900"/>
<wsa:allow type="load" from="http://localhost:9900"/>
</wsa:webScriptAccess>

Thanks,
Derek