quick question, what exact namespace, what exact 'serializable' attribute must be used?
I'm now getting class
Foo (Cat) is not marked as serializable, and it is. mmm!
quickest way to give you the feedback is for you to clone this 'gist' / spike repo and run the test
clone that, and checkout branch
fail2
the failing test is '\Tests\HelloOrigoSmokeTests.cs`
Put the ToArray() inside the Execute instead and it will work
Hi Robert, there's this one phrase I dont quite understand in the documentation, describing the RoyalFoodTaster,
If a command fails, the taster is discarded and replaced with a clone of the real model, without requiring full restore. More importantly, the real model is readable while the taster is being rebuilt.
if the real model is still readable, (and valid) then why bother with rebuilding?
If the royal food taster goes corrupt, you need to create a new one
Ok got it; I had a performance test that appears superficially to contradict this; and my problem was that my test model was wastefully keeping a transaction history in memory that was never being queried. This resulted in a linear growth of model size in memory, resulting in a long clone times. (That's my theory) going to remove the transaction table from memory, ... that can always be recreated by replaying all the messages (wow.. that's incredible! ) ...and that should = a test that proves how it all works. If this works, I'd like to offer it for consideration as sample code for the docs?
so far, it looks like the sample code is thin on 'best practice' examples, or examples that show with tests, why (and when) you'd choose A over B.
And by can of worms I mean the implemenation was messy, lot's of leaky abstractions
But i might be able to dig it out for you if you're interested in archaelogy :)
I do enough archaeology in the day job
are not working well here, seems like the needs to be open @meganaut
Crap I cant type on this phone...
Ping me on twitter, @robertfriberg
hey @/all we've started our journey reimplementing/porting origodb to dotnet standard. Wanna help? Check it out at https://github.com/devrexlabs/memstate or come talk to us at https://gitter.im/memstate