Imagery can be stored, and served, from anywhere on your network.
You do need to be aware of some simple network and security considerations.
Just like you "login" to your computer, so does the applications that you use. Sometimes they just "borrow" your login, but other times they use any number of system defined "user details". This is particularly the case for any server application.
Image Web Server operates under a defined user account. This account must have “read” access to the image files in order to serve them....
For Windows based installations, before installing Image Web Server you will want to check that you have Internet Information Services installed.
Internet Information Services is the free web server that is packaged with the windows operating systems....
If you are installing IWS on Windows XP - as a quick evaluation - you might want to increase the connection limits of IWS.
Windows XP Professional runs IIS version 5.1 and comes with a 10 connection limit....
When you deploy your web mapping application, you want it to run as fast as possible. There are a number of "tricks" you can use to make it even faster. Many of these tricks seem to be missed when people deploy websites (GIS based or otherwise).
HTTP compression. This can really shrink the size of your HTML, Javascript or CSS files. usually to about 20% of what they were originally. With GIS Mapping sites, there is usually quite a bit of logic going into the JavaScript end - so making your JavaScript files as small as possible is a real benefit. For example - iws.js - one of the main JavaScript files went from 140KB to just 29KB!
Minification of JavaScripts, CSS and HTML. Minification indicate the removal of excess or unnecessary whitespace or comments in your JavaScript or CSS files. Cutting out this space can reduce the size of a text based file by around 30%. With this size, I also strip out excess whitespace in the HTML files.
Minification often extends to renaming variables in JavaScript files to "shorter names", saving on size of data. I have had mixed success with this - sometimes it seems to create errors in my code.
Combine CSS and Javascript files. Reducing the number of individual requests for files speeds up data access. So, where possible I have grouped CSS and Javascript into one larger file, rather than separate files. Each file request can take up to 200 miliseconds. So, if you have 10 or more external scripts, it can quickly add to your total loading time.
Settings a long expires header on resources that don't change often. This means that a browser doesn't have to keep requesting the same resources over and over again - even if it is just to find out the resource hasn't changed. I have set a long expires on my icon images, as well as base JavaScripts, CSS files.
R....
| |