yeah, i agree that it's best to focus on making our serialization more efficient as a first priority. then see if there's anything else worth doing. i'm not 100% convinced that it's actually impossible to separate out the versioned components because we could record some kind of virtual object pointer to substitute for the reference that could be fixed up later (basically implement a very custom serialization mechanism that allows object references to span files), but at that point, i think we'd be writing our own highly wicket-specific serialization code from scratch and it seems like just doing efficient serialization with something like xstream as a starting point might be good enough to really improve things dramatically.
Agreed, let's start there. Eelco
