CODEWITHSUNDEEP
c++
Aquarius_Girl
Aquarius_Girl

Reputation: 22936

Remote logging library versus software(logger)

I am penning down the features that a remote logging library might need when built from scratch. I looked up this: http://www.aggsoft.com/serial-data-logger.htm

I wish to know that what differences can be between a remote logging library and a remote logger software.

Few things that I thought of:
1. The library can be used in C++ programs to log error messages on the fly.
2. The library will require programming knowledge on the end user's part.
3. The software cannot be used "inside" a C++ program, so we won't be able to log the error messages on the fly? Not sure about this one.

I would like to know that besides logging error messages, what are the things for which it makes sense to use the remote logging library? Sharing big files? Anything else than these two things?

Secondly which is better in what way out of a library and a software - in the current case?

Upvotes: 0

Views: 619

Answers (2)

Brady
Brady

Reputation: 10357

As I mentioned in the my comments to your question, I would think that a logging library would provide some sort of an API/SDK, whereas remote software would not. The same would hold true if its sending messages via TCP/UDP or a serial port. The difference between the 2 options would be how much coding you would have to do. That is, how much would you have to reinvent the wheel?

Upvotes: 1

wuliang
wuliang

Reputation: 749

IMHO, nearly all debug environment/tools support redirect the console output the serial port (using print, or other API). It usually not a a task of Application programmer.

There are other methods for "remote logging":

    1) syslog, syslog-ng 's remote service
    2) save log local, fetch using ftp

Upvotes: 0

Related Questions