Simplify resources snapshot to make our lives easier with the lift-json library.
After a few failed attempts with lift-json, I sacrifice the Map for a List.
Give the option of pretty or non-pretty json printing
Store the last update timestamp per resource and instance id
This code has some errors with JSON serialization
Add a few helper methods to resource event
Super documenter. Work in progress.
An attempt is being made to work the algorithms in plain prose.Hopefully, this will help everyone get a better understanding of thecomplexities involved and of the quite interesting problem domain.
As I said, this is Work in Progress...
Don't store the whole agreement to the user state
Store a reference by name instead.
Case objects instead of objects for cost policy definitions
The log string has 2 args, not 3
Use the list of resources defined in the policy
Store the newly created user actor in the LRU cache
View revisions
Also available in: Atom