I use the dynamic package and manifest imports, as Curl Help says...
let manifest:ComponentManifest =
{with-file-caching-style FileCachingStyle.resynchronize do
{import-manifest
manifest-url,
check-out-of-date? = true
}
}
let package:Package =
{with-file-caching-style FileCachingStyle.resynchronize do
{import-package
package-selector,
manifest = manifest
}
}
But one problem has occured : it cannot reload the imported packge.
Something strange is that if a manifest.mcurl file size is changed, the package can be reloaded.
I don't know what is wrong ...
Maybe you have missed something when reading the documentation, here is the text around the sample codes from documentation:
This explains why changing manifest file could help you reloading your package .
I think there is another informal way to help reloading package files:
add some codes before import-package like:
{do
{with-file-caching-style FileCachingStyle.resynchronize do
{read-from {url "path-to-your-package-file"}}
}
}
I believe this will reload your package file for sure. Add more lines if you need to reload more that one file like the above.
thank you
I missed the rest of comments of Help, but I dont understand its explanations, because the package can be reloaded by the trivial change of a manifest file.
I wonder also why the change of date of a manifest file can't reload a package file.
I would like to know more detailed Deng Tian's way of reloading a package.
I haven't yet fully understood what's your real problem is, becuase there are many factors that could affect your result.
The special way I wrote above is to ensure that the file will be re-downloaded from web server, instead of the one that has once been cached in browser cache on Windows, and this is usually not needed if you configured your settings related with resynchronization correctly for your Curl applet, including settings in your source codes and settings in Curl Control Panel on your client RTE.
Did you try with settings like the following in your applet ?
