Setup Cache

In the section covering the SCEX's Account module, it was shown how to list all of the accounts present in a given data directory path. In this chapter, a setup file is defined as the tuple (data path, account number).

As of the January, 2009 release of the SCEX, a setup file cache is initialized when the SCEX is first loaded. This cache will store setup files in memory, so that later calls to the SCEX which utilize cached setup files will not need to reload the files for each calculation, so long as the setup file remains in the cache. This cache will prove most beneficial to applications which allow access to multiple setup files, such as those commonly found in ASP and SAAS solutions and web hosted applications.

Sample Request

The following is a sample SCEX request for setup file cache information:

<inSETUPS Cmd="List" Arg1="all" Arg2="all" />

Much like the Account and Version module requests of previous chapters, this input query is made up of a single (empty) element with three (3) optional attributes.

Sample Response

No matter what Cmd attribute value is specified in the request, the format of the response is the same. The following is a sample response generated by the previous request:

<?xml version="1.0" standalone="no" ?>
<!DOCTYPE outSETUPS SYSTEM "outSETUPS.dtd">
<outSETUPS>
  <Setups Count="3" Max="100">
    <Setup Index="1" Path="c:\scex\" Account="2" LastUsed="00:00:16" UseCount="0" HitCount="1" />
    <Setup Index="2" Path="c:\scex\" Account="1" LastUsed="00:00:04" UseCount="0" HitCount="1" />
    <Setup Index="3" Path="c:\banks\" Account="9" LastUsed="00:00:24" UseCount="0" HitCount="1" />
  </Setups>
</outSETUPS>