Hi Werner, You're absolutely right. My "could" actually meant we must ;)
What we <could/> do though would be to automatically fail-over to normal state-saving and rendering, if the state grows too large. So we have an error, right, but the app doesn't stop working. The page just isn't bookmarkable anymore. regards, Martin On 1/27/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Martin Marinschek schrieb: > > We could optionally do that - don't know if that is practical. > > > > I've discussed with Manfred some more, and he suggests to do the following: > > > > give t:saveState an optional "bookmarkable"=true attribute, and with > > that decide on some of the state to be saved even though the > > tree-state is lost. > > > > we could also log an error to the user when the maximum url-size is > > exceeded. > > > > That error is definitely mandatory to avoid constant posts in the users > list why data gets lost ;-) > No in fact the size limitation is one of the reasons post usually is > preferred for form handling, such an error would help alot in a get > situation to track down problems. > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
