3.20.7. <zones>


<< Prev   Next >>

13.4.1.1. Item description

<zones> item is subordinate to <point> item. No more than one is allowed. <zones> item may have one or several subordinate <zone> items.

This item does not have any attributes.

3.20.7.1. <zone>

Each <zone> item describes one separator. The sequence of <zone> items in <zones> item matches the sequence of separators in Designer. If the sequence of separators changes, default.vrd file must be edited accordingly. Number of <zone> items must not exceed the number of separators. If the number of items exceeds the number of separators, an exception will be generated when connecting to the infobase. If the number of items is less than the number of separators, the default value for separator type will be used as a value of non-specified separators and the separator use will be disabled.

<zone> item may contain the following attributes.

safe

Allows or prohibits changing the values of objects related to data separation functionality, if the infobase is accessed by a web client or by a thin client via web server (data separation safe mode). This attribute must be used when the user needs to ensure that no other data regions can be accessed when accessing the infobase over the Internet.

Default value: false (changes are allowed).

If the attribute value is true, the following actions are prohibited in the session using this infobase publication:

  • Disable a separator if the separation is not conditionally disabled.
  • Change the used separator value if the separation is not conditionally disabled.
  • Modify objects managing the conditional separation:
    • Specified for the separator itself
    • Specified for objects included in the separator
specify

Determines whether the published infobase address must contain this separator value.

Default value: false (a separator is not used in the address).

value

Explicitly specifies the value of separator placed in this position.

If the value of the value attribute is not specified and the specify attribute is set to false, this is equivalent to the absence of the separator value (corresponds to the "-" value in the connection string Zn parameter value).

If the specify attribute is true and the value of the value attribute is specified, this value (case-insensitive) must be explicitly specified in the infobase address string in the respective position. Otherwise, error code 404 (web page not found) will be returned when attempting to access the infobase.

Characters that are not allowed in URLs (RFC 1738, https://datatracker.ietf.org/doc/html/rfc1738.html) are converted to UTF-8 and encoded in accordance with section 2.2. URL Character Encoding Issues of RFC 1738 standard (using "%" and two hex characters).

Default.vrd file example:

<?xml version="1.0" encoding="UTF-8"?>
<point xmlns=http://v8.1c.ru/8.2/virtual-resource-system xmlns:xs=http://www.w3.org/2001/XMLSchema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
base="/test"
ib="File=&quot;c:\base&quot;;">
<ws enable="false"/>
<zones>
<zone value="8214" safe="true"/>
<zone specify="true" />
<zone />
<zone specify="true" />
<zone value="last" specify="true" />
</zones>
</point>

5 separators are defined in the application in this example. The infobase address will be as follows:

http://example.com/test/01/20101231235959/last

It will be interpreted as follows:

  • http://example.com/test. Infobase address.
  • The first separator must not be specified in the address (default specify attribute value is false), its value is 8214, and it is not possible to control this separator programmatically (safe attribute value is true). The other separators can be controlled programmatically, as the safe attribute value for zone items is not specified and the default value (false) permits program control.
  • The second separator must be specified in the address (specify attribute value is true), and its value is 01.
  • The third separator is disabled.
  • The fourth separator must be specified in the address (specify attribute value is true), and its value is 31-12-2010 23:59:59.
  • The last separator must be specified in the address and its value must be last.

Such separator specification may be used for the thin client running via web server, for the web client, and for web services.

If different method of specifying the separator values to be applied during the session are used at the same time, these are determined as follows:

  • If default.vrd file contains the specified <zones> item, the separator values specified in the infobase address have the highest priority. Where:
    • Values specified in the startup parameter (Z parameters) are ignored.
    • Values specified in the infobase connection string are ignored (Zn parameter in ib attribute of <point> item).
  • If <zones> item is not specified in default.vrd file:
    • The attempt to define separator values from address string Z parameter is made.
    • If parameter is not specified, the attempt is made to use the values, specified in infobase connection string (Zn parameter in ib attribute of <point> item).
  • As a general rule, the separator value position priority is as follows (the priority decreases from top to bottom):
    • Infobase address (if default.vrd file contains <zones> item).
    • Startup command line (Z parameter).
    • Infobase connection string (Zn parameter in ib attribute of <point> item).

<< Prev   Next >>

Icon/Social/001 Icon/Social/006 Icon/Social/005 Icon/Social/004 Icon/Social/002