1) Will my keycode work with an updated version of Xload?
2) I have found a bug and submitted a report, what do I do now?
3) I have added my keycode programmatically to Xload and the software still operates as trial software?
4) Are Xload versions backward compatible?
5) How do I install the upload timer (progress monitor)?
6) I want to sell a software product utilizing your software inside my product, how do I go about this?
7) How do give you feedback or submit a feature request?
8) How do I get an updated version of my software (i.e. with bug fixes etc), but still use the same keycode?
9) How can I view the User License Agreement(s)?
10) The Progress Monitor(Upload Timer) seems to work in the end, but doesn't smoothly update?
11) How do I get Xload to work inside a JSP?
topA: Yes, as long as the update does not comprise an extended API. A keycode will work with the version of Xload it was purchased for, irrespective if a new patch has been released. For example, if you purchased a keycode for Xload version 1.2, then any updated version number that starts with '1.2' would function (i.e. 1.2_14, 1.2_16 etc) with your keycode. But, Xload version 1.3 and above would not work with your purchased keycode as this comprises a new product with an extended API.
topA: The Xload team will look at your bug report and decide how best to deal with the problem. If applicable a new updated patch for that Xload version will be released in due course, you should download this and use with your existing keycode. Although, there may be a delay as there may be a number of reasons that a new patch is to be released and so development in these areas has to be completed.
topA: There maybe a number of reasons for this. Firstly, make sure you have entered your keycode (case sensitive) correctly and it is for your particular Xload version. Secondly, make sure you have added your 'details' (that you entered when purchasing your license and that was sent with your license confirmation email) when setting the keycode programmatically. Without these, Xload will not become a full version. Thirdly, your backing store on your computer may not be available, meaning that Xload cannot store your keycode for you. To solve this, make sure you set the keycode (and details) at least once when your application starts.
topA: Yes, Xload version 1.3 will implement Xload version 1.2 API and more; Xload version 1.4 will implement the Xload version 1.3 API and more. Only when an Xload version is not supported anymore will API's be not supported.
topA: Refer to the documentation section of this website here or refer to the documentation that was sent with your downloaded bundle. look for the 'How do I' section which describes in detail how to setup the timer.
topA: You can purchase Xload with what is known as a bundling license. Please contact us for details here.
topA: You can give feedback here, good or bad, we want to hear from you. You can also submit a feature request here. Please be as descriptive as you can so that we can fully understand your requirements. Many thanks.
topA: You can use your keycode with any patch release for your version that you have purchased the keycode for. For example if you purchased your keycode for API version 1.2, it will work for any patch update for this version e.g. 1.2_16, 1.2_20 etc. It will not however work with a new API version (i.e. 1.3 when it is released).
topA: EULA's (End User License Agreements) can be viewed in any downloaded Xload bundle found on the downloads page.
topA: The Progress Monitor works by sending a seperate request to the Server. What we have found at Gubutech is that under certain conditions when one ip sends two requests to the same Server, the first request has to finish processing before the second one can be sent any response. This means that the correct information is being generated by Xload but the Server used is 'blocking' or 'serializing' the request. Unfortunately, there does not seem to be an easy catch all fix; most Progress Monitors work in this way (seperate requests for progress information) and you are best consulting documentation regarding your Server in this area or using a different server setup.
topA: Getting Xload to work inside a JSP is easy. You simply import the Xload package (com.gubutech.xload.*) and add ordinary Xload code as scriplets inside the JSP. An example of this can be seen here. Gubutech microsystems are working on a revolutionary purely TAG based approach allowing non-Java Programmers to harness the power of Xload by using just Tags with processing logic built in. This will provide a highly flexible and powerful solution allowing file upload processing software to be built very quickly, reliably and easily in the future.