Hi Stephan,
Your suggestions are very interesting. I think we should pick a couple of
paths we can tackle with minimal effort and start there. I am happy to help
in getting this effort started (maybe we should have a Skype discussion?)
My comments are below...
D.
On Wed, Apr 29, 2015 at 3:35 AM
The current aim is the first option as you have correctly derived. :)
On May 1, 2015 5:39 PM, "Aljoscha Krettek" wrote:
> From this discussion I derive that we will have a state abstraction that
> everyone who requires state will work with? Or will the state be in object
> fields and they will be
>From this discussion I derive that we will have a state abstraction that
everyone who requires state will work with? Or will the state be in object
fields and they will be saved upon invocation of some doBackup() method.
On Apr 30, 2015 10:31 PM, "Stephan Ewen" wrote:
> That would be one way of
