Provide useful logging in cli_wallet

[jmjatlanta]

User Story
As a cli_wallet user, I want to have a log of the communication between the wallet and the API server.

As a developer, these logs can assist in solving reported problems and debugging software problems.

Impacts
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below)

Additional Context
See #1528 (comment)

CORE TEAM TASK LIST

• Evaluate / Prioritize Feature Request
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation

[jmjatlanta]

@cogutvalera please provide an estimate of what it will take to implement this.

[cogutvalera]

@jmjatlanta Thank you very much ! I want to take this issue ! I will estimate this issue soon ...

[abitmore]

IMHO this has been done via #1528. I created #1570 for another needed feature.

[jmjatlanta]

The intent was that #1528 solves a bug that prevented logging from actually happening. But the logging that was created was not very useful. As your comment at #1528 (comment) suggests, it would be better to log some details of the communications between the client and server.

It looks like #1570 is between the another app and the wallet in daemon mode.

Am I misinterpreting the intent of your comment in 1528?

[jmjatlanta]

Closing this in favor of #1570

[oxarbitrage]

closed by #1528