Enhanced Performance Option with IConnectorAccess

You can significantly improve the performance by caching the task file's XML metadata so that it does not have to be reloaded and parsed every time a task contained in the task file is opened.

To enable caching

• Append a URL-style argument to the end of the metadata file name in the open call.
  For example, myConnector.open("c:\myMetadata.xml?cache=true");

• You can append additional parameters by using '&' between each parameter.
  For example, <my metadata>[?<param 1= value 1>][&<param 2= value 2>]...[&<param n= value n>]

  The parameter delimiters '?' and '&' can be used interchangeably, but the standard usage is '?' for the first parameter, and '&' for subsequent parameters. There is no limit to the number of parameters that can be used.

• The only parameter other than cache which is currently defined is instance. The"cache" parameter and the "instance" parameter can be used together. The instance parameter is sometimes used for dedicated LU support, by specifying a particular LU name.

To update caching

If you copy an updated metadata file to a running system with caching enabled, you need to update the cache. There are several ways to trigger an update.

• Update the metadata file and simply restart each Java VM that is hosting a connector. All connector instances will automatically start using the updated version when the VM is restarted.

• Without restarting the Java VM, you can call open on any connector instance with cache=false. All connector instances will automatically start using the updated version. Repeat for each Java VM that you want to update. The open parameters syntax is: <path to metadata XML>[?cache=<true | false>]...[&=<value n>]

To disable caching

Use myConnector.open("c:\myMetadata.xml?cache=false"); or omit the "cache" parameter. The default value is False.

	Building Applications Using Native Win32 Technologies
	Proxy Service Interface API Reference