tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hanson Char <hanson.c...@gmail.com>
Subject Re: table layout of radio buttons and others
Date Sun, 13 Mar 2005 09:07:54 GMT
> Back to ron's question: once this feature is in, Table, among other
> components, could store the state in the URL and make your app stateless. 

There is a length limitation as to how far a URL can go.  When you say
"store the state in the URL", do you also mean the storing
automatically in the form of hidden fields to bypass the length
limitation ?  Otherwise, it won't work in the general case.

H


On Sun, 13 Mar 2005 10:26:03 +0200, Mind Bridge <mindbridgeweb@yahoo.com> wrote:
> Hi,
> 
> > It would be great if you could take a look at my posting at the users
> > list regarding NullTableSessionStateManager :)
> 
> If I understand correctly, you want the sorting and paging information to be
> stored in the URL, rather than the session.
> 
> NullTableSessionStateManager is an implementation of
> ITableSessionStateManager that simply tells the component not to do extract
> the state information at all. You are probably more interested in
> ITableSessionStoreManager instead, even though it would not help at the
> moment either (as described below). It usually is used to manually store
> that information somewhere else, like in the Visit if it is to be shared
> among multiple pages.
> 
> At the moment, unfortunately, Tapestry has NO mechanism to persist
> information in the URL (rather than in the session), either as persistent
> properties, or in any other form. This is a feature marked for 3.1, but it
> is not there yet either. Howard has done almost everything related to it,
> but that final step is missing.
> 
> Again, there are a hell of lot of things dependent on that very feature, as
> described in other emails on this list.
> 
> *** Howard, do you plan to add that soon, given that what has been
> implemented so far is almost there? Or should I do it myself, following what
> you've done?
> 
> Back to ron's question: once this feature is in, Table, among other
> components, could store the state in the URL and make your app stateless. It
> will also be possible to do that by providing your own implementation of
> ITableSessionStoreManager relatively easily. At the moment, however, I am
> afraid that is a problem.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message