On 11 Oct 2006, at 21:13, Eelco Hillenius wrote:
I'm not really clear how responsibility /can/ be delegated to the
components? Would they just serialize the model into the URL? Can't
help thinking this would lead to some seriously long URLs, even for
detachable models (class name has to be in there, for a start).
It would work like I started my email with.
It is not my intention to serialize all state of the components/
models. This is the 'brute force' approach of JSF and .NET (yes I know
somewhere down the line it is probably somehow configurable :) ).
Stateless components currently just don't keep any state you put in
them. Much like .NET or Tapestry where you can put all the variables
you want in the pages, but the page will be recreated on each call.
State you want to transfer must be put in ViewState (.NET), or
configured/ annotated (Tapestry). This optional state thingy is
something I'm proposing here for Wicket.
Ahh, right, I'm with you. I'm totally in agreement that brute force
serialisation is a bad plan -- I was thinking more of serializing the
'state' of detachable models, but you're right, that should be
reconstructable when the new request comes in anyway, since we're
talking primarily about static information like property resolver
paths etc.
P.
