cli_wallet caching issues

[vikramrajkumar]

From @theoreticalbts on January 21, 2016 20:44

The cache design of cli_wallet is fundamentally broken, leading to numerous issues: cryptonomex/graphene#323 cryptonomex/graphene#331 cryptonomex/graphene#353 cryptonomex/graphene#527

Anything which updates the account object causes a tendency for the cache to get out of sync. Really the CLI wallet should use the same architecture as the web wallet: Subscribe to object updates in order to implement a caching proxy for all object requests from individual wallet functions. As a stop-gap we could simply remove the existing cache, implement a new cache and require it to hit the witness_node anytime it needs an account (assuming most cli_wallet users also run witness_node on localhost or a fast LAN).

As this requires a substantial re-working of the wallet, perhaps this should be a worker proposal.

Copied from original issue: cryptonomex/graphene#530

Tasks to be done:

• internal get_account function
• list_my_accounts
• account_id change when there is a fork (is this a separate issue?)

[vikramrajkumar]

From @neura-sx on January 22, 2016 7:46

Maybe a simple resync() command would be a good temporary fix?
This command would force the CLI's cache to be reset.
Not perfect but it still better than having to start over the whole process.

[ryanRfox]

Assigning to @cogutvalera to review the original Issue(s), impacted code and draft a description of a proposed task list to seek approval for further development. The need on this Issue is to define what we want the fix to be and how we get there without breaking current functionality. Please be descriptive in your assessment and proposed solution options.

[cogutvalera]

ok sure ! Thanks !