|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|Note: download coming soon...
Note: download coming soon...
1. Downloading the XAP zip file
Download the ZIP or TAR versions of the file from the [http://incubator.apache.org/xap XAP Apache site].
2. Unpacking to your web server document directory
Locate the document root for your web server. If you do not have a web server, you can download one for free from [http://httpd.apache.org/]. The document root for Apache web servers is indicated in the conf file with the DoccumentRoot variable, and is called htdocs by default. For IIS the document root is under INetPub\wwwroot.
Create a subdirectory under your document root and unpack the contents of the downloaded file into this subdirectory.
For more information consult the documentation of your web server.
3. Running the initial example
Open up your web browser and navigate to this directory. You can typically do this using [http://localhost]. Locate ajax-index.html and run in your browser.
Image Caching and IE 6
Dynamic user interface powered by Ajax uses images to enable the much of the dynamic nature of the UI; this involves gettinga and setting images rapidly on the fly. IE 6 has a limitation with image cache - it does not check it for images, instead getting the image on the server. This is discussed here and various other places. The workaround is to configure the web server not to add an expires HTTP header.
Cached XAL files
XAL files are cached by the browser. This means that refreshing your application page will not get the latest copy of the XAL file that was edited. This can also be managed by the web server. Another way is to add the header to the page, possible if using server side script technology such as JSP or PHP. In PHP this can be done with: header ( 'cache-control: no-cache' );
Deploying XAL files to IIS
IIS does not recognize files with a .xal file extension and does not send them by default. This can be worked around by setting a mime type for XAL text/xml; another workaround is to rename the files with a .xml extension. This behavior does not exit on any application servers or on Apache web server.