Differences

This shows you the differences between the selected revisions of the page.

2011-07-31 2011-09-15
scriptcommand_* (martin) bug 545 result in session (martin)
Line 25: Line 25:
The top level ''session'' tag represents one logical session, which may consist of several physical sessions, particularly when connection is lost. Attribute ''name'' refers to name of the logical session. Attribute ''start'' indicates time when the session was initiated ((All timestamps in XML log have XML ''dateTime'' type, where only ''YYYY-MM-DD"T"HH:MM:SS.NNN"Z"'' syntax is used.)). The top level ''session'' tag represents one logical session, which may consist of several physical sessions, particularly when connection is lost. Attribute ''name'' refers to name of the logical session. Attribute ''start'' indicates time when the session was initiated ((All timestamps in XML log have XML ''dateTime'' type, where only ''YYYY-MM-DD"T"HH:MM:SS.NNN"Z"'' syntax is used.)).
-The ''session'' element includes [[logging_xml#elements|child elements]], where each element represents single log entry, i.e. single physical operation with remote file over the logical session.+The ''session'' element includes [[logging_xml#elements|child elements]], where each element represents single log entry, i.e. single physical operation with remote file over the logical session. In case the connection is not established, the ''session'' element includes single ''[[logging_xml#result|result]]'' element with the error (&beta_feature).
===== [[operations]] Representing Operations in Log ===== ===== [[operations]] Representing Operations in Log =====
Line 41: Line 41:
XML log may not include some errors, even if they occur, for two reasons: XML log may not include some errors, even if they occur, for two reasons:
  * The operation that failed does not have corresponding log element (see [[logging_xml#operations|above]]).   * The operation that failed does not have corresponding log element (see [[logging_xml#operations|above]]).
-  * The error is not associated with particular physical operation. Simple example is authentication failure. More treacherous example is failure to list remote directory, to find list of files it contains, while downloading the directory. This error occurs during download operation, which is logged. But as download of individual files is logged only, the error is not associated with download of any particular file. So it will be absent from the XML log.+  * The error is not associated with particular physical operation. Treacherous example is failure to list remote directory, to find list of files it contains, while downloading the directory. This error occurs during download operation, which is logged. But as download of individual files is logged only, the error is not associated with download of any particular file. So it will be absent from the XML log.
With some protocols, each of the physical operations are performed individually. With some protocols, set of operations may be performed in atomic form. This may prevent mapping error to specific operation. In this case the error may be associated with more operations, resulting in its duplication in the XML log. With some protocols, each of the physical operations are performed individually. With some protocols, set of operations may be performed in atomic form. This may prevent mapping error to specific operation. In this case the error may be associated with more operations, resulting in its duplication in the XML log.
-Result of an operation is represented by child ''result'' element of respective operation element. The ''result'' element has boolean ''success'' attribute.+Result of an operation is represented by child ''result'' element of respective operation element or top level ''session'' element. The ''result'' element has boolean ''success'' attribute. Note that top level ''session'' element includes ''result'' only in case of failure (&beta_feature).
<code xml> <code xml>

Last modified: by martin