TLOG 1.0 NO IDEA Avatar
  1. OMG Issue

TLOG — Section: 1.2.5.1

  • Key: TLOG-59
  • Legacy Issue Number: 9262
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • Summary:

    The specification says that "The write_recordlist() operation is provided ass a convienience operation to allow the output of a query of one log to be written to another log. In this case, only the "info" field (event content) of the RecordData struct is written to the log, the LogRecord id and logging time will be assigned by the log.". This is the only place in the spec that RecordData is used, I believe that LogRecord was intended. Also, it is unclear whether the attr_list field should be copied. While it says "only the info field" is written, attr_list is among the fields listed that will be "assigned by the log". For what it's worth, the Orbix Log Service implementation appears to copy the attr_list. Their Enterprise Messaging Guide for ORBIX 6.2 says "write_recordlist() is functionally identical to write_records(). It writes data directly to the log and raises the same exceptions. The major difference is that the record's data is stored in a LogRecord. This allows you to add a series of name/value pair attributes to assist in querying the log". The TAO log service implementation, which I currently maintain, also copies the value of attr_list.

  • Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT