Sounds very good indeed! Mathias - absolutely professional as always ;)
Werner, you did have a need for such a thing as well, right? So you might check this out a bit? regards, Martin On 10/18/05, Mathias Brökelmann <[EMAIL PROTECTED]> wrote: > Well, I have not taken a look into the ri for this issue. So I can not > say if it is solved like the ri. > > This is what I have done: > > If server side state is uses the serialized view is now really > serialized (this was not the case before) into the session by using > the viewid and a sequence number. The sequence number will be rendered > into the response (either as a hidden input field if used in forms or > as a param in a url). This sequence could also be used for other > things since it is increased by every request. The last sequence used > is also stored into the session. > > To restore the response the viewid and the sequenceid from the request > is used to determine the serialized view. The last 15 (currently fixed > number) views will be saved into the session. I´ve utilized a > ReferenceMap which uses SoftReference instances for the views after > the 15th. So if the garbage collector doesn´t collect these values > they are still available. > > I´ve done some testing so it seams to work. If anyone (maybe you > Marting ;)) finds the time to make some more tests I would be very > happy. > > Best Regards, > > Mathias > > 2005/10/18, Martin Marinschek <[EMAIL PROTECTED]>: > > Mathias, > > > > wow - you have solved the server side state saving problem we have had for > > ages? > > > > That will make some users very, very happy! > > > > Thanks from the whole team, great news indeed. > > > > Do you want to give us (on the dev list) a short wrapup on how you > > solved things? Did you keep close to the RI or did you implement a > > different solution? > > > > regards, > > > > Martin > > > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
