#: Johan Compagner changed the world a bit at a time by saying on 9/16/2005
11:50 AM :#
Action part is the part where the listeners are being called (lets say the
Swing Action.actionPerformed() method)
For example the action part is the Link.onClicked() or the Form.onSubmit()
(models updated/ database updated)
That action will result in a response page set.
After that we get the rendering/response part. And now the render strategies
are kicking in.
You have 3 kinds how a response page that was set by the action phase will
be served to the client
1>
in the same request (ONE_PASS_RENDER) so the aciton part and the response
part is done in the same http request.
drawback. The url the users sees is mostly a ugly one (the get or post of
the link/form) and you have the reload button problem
where the user can submit the things he just submitted again.
2>
in a redirect request (REDIRECT_TO_RENDER) so the action part set a response
page. The response phase is first sets
a redirect url. And that will after the client side redirect (a second http
request) serve the response page. reload button problems are fixed by this
But all youre models are attached and detached once more. And listviews can
only build in the redirect response phase there table
so the page structure is changing (or can change) then twice for one submit
a user did. (bad for clustering)
3>
and we have the combo this is the default (REDIRECT_TO_BUFFER) this has the
best things of both worlds. No reload button problems
because we do a client side redirect. But the rendering of the page itself
is already done in the first request and stored in a buffer until the
redirect is there again)
because of this models are only attached and detached once. Listviews only
alter pages in one request not 2.
Thanks a lot Johan. Now it makes a lot of sense to me too ;-).
This is the best thing to do for almost al situations except a non sticky
cluster environment. Because the redirect can then hit a different server
where the respone buffer was not build.
But with not sticky session cluster environments can only really use setting
1.
Can you explain more of what a sticky/non-sticky cluster env is?
./alex
--
.the_mindstorm.
On 9/16/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
Hi!
I have started to take a deeper look at Wicket as it is approaching the
final 1.1. However I haven't
worked with it so far, but I would like to say that till now I like it.
The following questions have probably been already asked, but
unfortunately I couldn't find the
answer on the wiki or on gmane.
what are render strategies used for? by reading the javadocs I always see
action part, render part:
what is the meaning of these 2?
thanks in advance for any hints/links and your help,
:alex |.::the_mindstorm::.|
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
