Team, It turns out that the ability for a CAS registry to persist changes between redeployments is a needed and pretty useful change for a relatively modest CAS deployment. I would like to propose that we swap out the default memory-based implementation with one that is able to carry changes across server restarts, so the behavior would become less confusing and more natural for new adopters who may not immediately realize the fact that changes may be lost. We have several options with JSON and embedded databases each with their own pros and cons. What makes the most sense?
Misagh -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
