"Clemens Zeidler" <clemens.zeidler@xxxxxxxxxxxxxx> wrote: > Yes at least for the Archive() part its sounds reasonable. I can just > add > the geometry part to the default BApplication Archive function. One > disadvantage here is that in some cases the geometry data will be > stored > twice. [...] Not sure if I can follow you here. Why should an app ever need another way than the system delivered for storing stuff the system should take care of? Also, why should BApplication take care of this at all? A BApplication always has a list of all windows - I'm not sure if it's a good idea, but you could just archive all windows with it. An application that would want to support the session management would just need to make sure that its (un-)archival functions are correctly implemented, and also recreate the model side of things. Bye, Axel.