Code Interpretation tars framework (five) chapters framework. Log service LogServer, AuthServer, patchclient concise and other services

LogServer log service

This seems to be nothing to see.

Worth introduce is the log file is generated where.

Business services specified log file will be in / log <logpath> / tars configuration place. . Official to the template configuration file is / usr / local / App / TARS / remote_app_log . . This path.

Under this directory :

sLogPath = _log_path + "/" + app + "/" + server + "/" + logname..

For more details of the data. Available to fix it.

 

 

AuthServer Authentication Service

The feeling is not a complete version provided. Very casual.

table seemingly long :

id | int(11) | NO | PRI | NULL | auto_increment |

| application | varchar(128) | YES | MUL | | |

| server | varchar(128) | YES | | NULL | |

| objname | varchar(128) | YES | | | |

| token | varchar(128) | NO | | | |

It provides only plug into a table App-Server-objname: token . . This key: value curd interface. .

I do not understand why such a practice. .

 

patchclient patch Services client library

This totally did not understand is doing a

I did not see where to use this stuff

 

Guess you like

Origin www.cnblogs.com/yylingyao/p/12198429.html