<?xml version='1.0' encoding='UTF-8'?>
<ca version="1">
    <!--
        Channel Access client configuration
        ===================================
        
        The core parameter for Channel Access are configured through
        the JCA Context. This includes what implementation of JCA is used
        (JCA-JNI or CAJ-PureJava) and the configuration parameters for those
        implementations.
        
        By default, CAJ is used with the default CAJ configuration.
        CAJ should, by default, honor the standard EPICS environment variables
        to configure the client. One can still override that configuration
        by specifying the configuration properties here. Please, refer
        to the JCA/CAJ instructions for details on these properties.
        
        We recommend to use the CAJ (pure java) implementation, as the JCA (JNI)
        implementation currently lacks an official maintainer.
    -->

    <!-- This examples uses the pure java implementation (CAJ) with the given
        configuration parameters -->
    <!--<jcaContext pureJava="true" addr_list="" auto_addr_list="true" connection_timeout="30.0"
                beacon_period="15.0" repeater_port="5065" server_port="5064"
                max_array_bytes="16384" />-->
    
    <!-- This examples uses the JNI over C implementation (JCA) with the given
        configuration parameters -->
    <!--<jcaContext pureJava="false" preemptive_callback="true" addr_list="" auto_addr_list="true" connection_timeout="30.0"
                beacon_period="15.0" repeater_port="5065" server_port="5064"
                max_array_bytes="16384" />-->
    
        
    <!--
        Channel Access data source options
        ===================================
        
        The data source itself si configurable through the following parameters:
        
        monitorMask - this allows to change what is the mask used for
            the CA monitor. The possible values are:
                VALUE (default) - corresponds to a monitor mask on both VALUE and ALARM
                ARCHIVE - corresponds to a monitor mask on LOG
                ALARM - corresponds to a monitor mask on ALARM
                [int] - a numer corresponding to the mask itself
        dbePropertySupported - whether to subscribe to DBE_PROPERTY to monitor
            metadata chances. Possible values are "true" or "false". The default
            is "false" (the safe chioce since old versions of EPICS do not handle it)
        honorZeroPrecision - whether zero precision on numberic metadata should
            be used or disregarded. This may be useful if too many IOCs are not
            configured propertly. Possible values are "true" or "false". The default
            is "true".
        rtypeValueOnly - whether .RTYP should be monitored as value only or not.
            this is a workaround for old IOCs. Possible values are "true" or "false".
            The default is "false".
        varArraySupported - whether variable length arrays are supported by
            the client. Possible values are "auto", "true" or "false". "auto"
            tries to detect the version of the client and act accordingly.
            Auto detection may not work on JNI implementation.
    -->
    
    <!-- Example to configure the dataSource option -->
    <!--<dataSourceOptions monitorMask="VALUE" dbePropertySupported="false"
                       honorZeroPrecision="true" rtypValueOnly="false"
                       varArraySupported="auto" />-->

</ca>
