===================================================== HeathCO Software- ----------------- QuickServ v2.5 Usage (Last update from v2.15) Copyright© 1999 HeathCO Software All Rights Reserved. ===================================================== Visit QuickServ on the net: http://www.heathcosoft.com/products/quickserv/index.html This file contains instructions to use QuickServ. ===================================================== CHANGES: (Since version 2.15) - Added a much faster preloading engine. - Fixed a few bugs with the registration algorithm. - Optimized performance for IE and Netscape ----------------------------------------------------- NOTE: To use QuickServ, you should have a basic knowledge of how to implement java applets into a website. Visit http://java.sun.com for more information. Installation: ------------------- Installing QuickServ is very simple. Simply download the QuickServ .zip file (http://www.heathcosoft.com), and you should see two files: 1) QuickServ.class 3) QSLogo.gif Upload these files into your web directory- (Notice: Preloader.class is no longer needed) Implementation: ------------------- Implementing QuickServ is also a very easy task. In the web document you want QuickServ to run on, simply insert the necessary applet code. You must have a knowledge of the tag to do this. Visit http://java.sun.com or http://www.heathcosoft.com for more information. The basic HTML for QuickServ should look like this: -The codebase is the directory that QuickServ is in One neat trick to make the applet invisible is to define the width and height as zero. Parameters: ------------------- Here are the possible parameters for QuickServ: 1) RegID - This parameter is required for QuickServ to function correctly. If you haven't purchased QuickServ, and are trying out the demo version, you must set this parameter to be: Otherwise, if you've purchased QuickServ, you should have received and registration code in your email after HeathCO Software has received your payment. Use that registration code for this parameter. 2) autoload - This parameter is used to specify whether or not QuickServ will begin preloading right away, or whether it will wait for the user to click on it before it starts preloading. To enable this feature, simply declare: Otherwise, omit this parameter if you want the user to have to start the preloading hisself, and disable the automatic preload. 3) redirect - This parameter is used to redirect the user to another website after the preload has completed. To enable this feature, simply declare: Otherwise, omit this parameter if you don't want the user to be redirected to another site. 4) item - This parameter is used as a set of parameters incremently. This is the heart of QuickServ, telling the applet what you want to preload. The demo version can only preload five links/files, while the licensed version can preload an unlimited amount of links/files. Here is a simple example using the 'item' parameter: ... etc ... As you can see, the first item preloaded is 'item0' and you can go on incremently, item0, item1, item2, ... etc ... NOTE: The only time you can omit the item parameters are when you are preloading from a text file, which is described next. 5) file - This parameter is optional, but either this parameter or a set of item parameters must be used. The file parameter defines a link to a text file that contains a list of URLs to preload. In many cases, this is a great option if many of your pages should preload the same files. Here is how you can use the file parameter: In the file preload.txt, you would have a list of URLs to preload, something like this: http://www.yoursite.com/file1.html http://www.yoursite.com/image1.gif ... etc ... Each URL in the preload file should be on its own line. ------------------------------------------------------------ Try all that stuff out and see how it works for you. We've tried to make it as simple as possible. If you have any problems, you can visit our website at http://www.heathcosoft.com or email john@heathcosoft.com We'd also love to here your comments on how it works out, and any recommendations for future versions! ------------------------------------------------------------ John Heathco john@heathcosoft.com HeathCO Software - http://www.heathcosoft.com