In many cases, it is useful to load XML from another file on your web server or from another web server entirely and manipulate it with XML for <SCRIPT>. With JavaScript, the former is possible with a little effort. However, the latter is impossible due to the JavaScript security sandbox your code must live in. This makes it impossible, for example, to load and manipulate an external RSS news stream directly from JavaScript.

XML for <SCRIPT> attempts to make both loading files from your server and from external servers both possible and simple. It does this by abstracting the many different methods for browser-server communications in a simple-to-use API. To allow for XML to be loaded from external domains, XML for <SCRIPT> provides a number of server-side proxies that load the external XML on behalf of the JavaScript and returns it to the browser in such a manner that reading and manipulation is possible. See the documentation for more details on the implementation of this feature.

NOTE: SourceForge.net does not allow outbound connections from their hosting servers. Sadly, this makes it impossible to demonstrate XML for <SCRIPT>'s proxies from the SourceForge hosting environment. If you would like to see this tool in action, please download and install one of XML for <SCRIPT>'s available proxies to your own web server and run the xmlIOProxy Test Suite from that machine.

For your convenience, you may also download the Java Proxy Reference Implementation (available from the download page) to quickly set up an environment for the demonstration of this tool.

You may find more information about XML for <SCRIPT>'s available proxies and the Java Proxy Reference Implementation in the "Documentation" -> "Server-Side Proxies" section of the web site.

This limitation is specific to SourceForge only, and is not a limitation of the proxy in any way.