Xvcl And Static
CjOS Project @ cjos.sourceforge.net
Index
Bind Pages
Cjos Library
Cjos Pages
Cjos News Pages
Eric Pages
Introduction To Smart Api
Osgi Pages
Registry Api Pages
Smart Api Pages
Xvcl Pages
CjOS Project
Summary Page
Mailing List
Download
CVS
JOS Technical Edition
Support This Project
Xvcl Pages; [ Cjos Audience]

Summary

Multiple, concurrent, independent instances of an XVCL Processor should be supported.

Test case

In an Ant script, we are running four XVCL Processors concurrently. Each processor is independent. 

 <target name="xvcl-parallel" depends="taskdef">
   <parallel>
     <antcall target="xvcl-1"/>
     <antcall target="xvcl-2"/>
     <antcall target="xvcl-3"/>
     <antcall target="xvcl-4"/>
   </parallel>
 </target>

Options

Command line options and other run-time properties are stored in the options table. When parsing the "command line", XVCL stores command line options in the OptionTable. The OptionTable reads the config.properties resource and stores properties in the OptionTable. In version 2.07 (1i), XVCL has-a FrameParser. In turn, FrameParser has-an OptionTable. Each instance of XVCL has-a separate instance of OptionTable. Therefore, currency is supported, and should be.

In version 2.07 (1a), OptionTable is static. Every instance of XVCL shares an instance of OptionTable. Therefore, concurrency is not supported.

Reference