> I read some more on the Bamboo.Prevalence API and I have a
> better (yet still
> fuzzy) image on what this is. Looking at some code samples, I
> could see how you can turn your data classes into a prevalent
> system. This change is minor, even for a complex project. The
> real challenge relies on changing your start-up routine so
> that the system can recover from the previous
> (unexpected) shut-down. Given a complex process, with lots of
> tasks that may or may not be synchronized, I find challenging
> to pickup from where you left, especially if you didn't
> design with this thought in mind.
I always say: there must be a reason why systems like Oracle, DB2 and
SqlServer use disk-based transaction logs. I.o.w.: IF
you decide to place the application state inside a relational database (and why
wouldn't you, they're designed for that), your
application state is well protected and you have all the tools at hand to
restore an application with an application state which is
known to be solid and fully recovered.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
