Changes between Initial Version and Version 7 of Ticket #903


Ignore:
Timestamp:
Jun 30, 2015, 7:51:47 AM (9 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #903

    • Property Status new → assigned
    • Property Cc Alex Dumitru added; adumitru removed
    • Property Summary Use already existing rasdaman loggin mechanism in rasnet → Use already existing rasdaman logging mechanism in rasnet
    • Property Priority minor → major
    • Property Milestone → 9.1
    • Property Owner changed from George Merticariu to Vlad Zamfir
    • Property Type defect → enhancement

  • Ticket #903 – Description

    initial v7  
    1 Remove easylogging and use existing rasdaman logging.
     1Right now debugging info is produced in few different ways:
     2 * RMDebug macros (RMDBGENTER, RMDBGEXIT, etc.), very complex and allow fine grained control, but seem somewhat broken
     3 * ENTER/LEAVE/TALK - very simple, provide indentation, but only global control is possible
     4 * The tile cache introduces TENTER/TTALK/TLEAVE which allow to turn on ENTER/LEAVE/TALK selectively only in the tile cache
     5 * RMInit::logOut, RMInit::dbgOut - simple output to the log, no possibility to turn off, typically used for outputing warnings/errors and other important info
     6
     7These should be harmonized into a single method, which is hopefully both powerful and simple.
     8
     9The decision in this ticket is to substitute all these with easylogging, already used in rasnet.
     10The main arguments for using easylogging are the following:
     11
     12- It provides thread safe logging.
     13- It can be configured at runtime by providing a configuration file.(e.g. log formats can be configured, log levels can be disabled if they are not of interest)
     14- It offers a range of different log levels.
     15- There is no clear documentation on what loggers are available in rasdaman and what capabilities they have.
     16