All Kinds of Methods for Persisting Objects
Richard Sperko · Apress eBooks · 2003
It was the best of times , it was the worst of times. For months, the development team I was working on had been writing a large Java system to support utility companies. The best part was working on a great project with an innovative team. We had built our own storage mechanism for the system, and that is what sometimes made it the worst of times. The storage mechanism included hundreds of classes, all with one purpose: to make our objects persistent (which means that the objects exist even after the application is done running). We could always re-create or use any object we wanted kept around. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.