again i ask. give me an example the only thing i can think of is having client side validatiors (so our validators also have a client part besides the server part)
What else is there that would benefit from this without a server call being made. johan On 4/4/07, Neeme Praks <[EMAIL PROTECTED]> wrote:
Matej Knopp wrote: > But wicket is a framework that manages server side state. That is quite a strong statement and I do not see it backed up by "official" Wicket "marketing story". http://incubator.apache.org/wicket/introduction.html Wicket is all about writing modular web applications in java, with all the benefits that come with the strongly-typed language. The word "server" is rarely mentioned in the documentation and "server side state" is an implementation detail. If we can write modular web applications in java and publish parts of them as JavaScript to be run in the client, thus reducing the amount of server state - I think this is still Wicket. Rgds, Neeme
