Yep, this is something we all are trying to achieve... The same old
purty framework, but with additional options to service the needy
greedy :-)
I could envision an IEncodableModel interface:
interface IEncodableModel {
PageParameters encodeState();
void decodeState(PageParameters parameters);
}
that would externalize its state into the page parameters, which can
be added to the component listener thing. Sort of a detachable model,
but then storing its state into the request url, instead of the
session.
I'm not sure this would help in any way, but I'll have it process in
my background...
Martijn
On 10/11/06, Paul Russell <[EMAIL PROTECTED]> wrote:
On 11 Oct 2006, at 20:06, Eelco Hillenius wrote:
> I'd like to chip in here to state that by what I proposed I don't want
> to make Wicket suddenly a stateless framework or something.
What you're proposing sounds good to me (a complete novice, I must
emphasise), but I think you hit the nail on the head there. Wicket is
fantastic for the work I'm doing precisely because it /is/ stateful.
I'd hate to see wicket going down the route of obsessing over the
reduction of server-side state management, because it'd lose a lot of
its appeal in the process.
Thanks,
Paul
--
<a href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a>
for <a href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a>
at the <a href="http://www.thebeststuffintheworld.com/";>Best Stuff in
the World!</a>
