Non-serializable types or control over serialization?

Apr 22, 2013 at 1:55 AM
I know you have the NonPersistentAttribute, but I'm not sure this suffices. I'm planning to use NDatabase as a persistent store for a distributed system, so the actors that are running have various wait handles that need to be restored. [NonPersistent] doesn't seem like enough here, since after a backup is restarted, agents need their wait handles intact. How would you imagine handling this scenario in NDatabase?

Sorry for the barrage of questions, this is the last one for the night, promise. ;-)
Apr 29, 2013 at 7:14 AM
I raised the ticket ( about adding possibility to have own serializers, so if that's addressing your problem, please vote for it.

Apr 29, 2013 at 2:05 PM
Yes, that should do it, thanks. Voted.