PROTECTED] ;
wicket-user@lists.sourceforge.net
Sent: Thursday, May 03, 2007 7:27 AM
Subject: Re: [Wicket-user] Sessionless Wicket?
detachable models are a must.
in my experience a wicket page is only about 50kb on average. that
would hardly cause an OOME on a server. 1.3 has
Yeah, you can give provide a HINT that they shouldn't be stored (that
they are stateless) by overriding getStatelessHint on the components
you put on the page. Note that if there is just one stateful component
on the page, that'll trigger the page to be marked as stateful UNLESS
you
i thought even if you explicitly mark a page as stateless that has stateful
components ( link, form, etc ), it
would still render as stateful ( creating session ) ? isn't that
the behaviour?
yes that is true.
Eelco
Should I be concerned that the numbers in the following URLs jump so much?
This is on a page signed in as an admin, where I do have some callback links
that are stateful.
On one page view, here is an admin link:
that is actually the page id not component id. so either you create 1500
pages in between, or stateless pages generate random ids - which it didnt
look like from the code...
-igor
On 5/4/07, Jeremy Thomerson [EMAIL PROTECTED] wrote:
Should I be concerned that the numbers in the following
In 1.3 you can use stateless pages (with stateless links and stateless
forms). However, you'll have to sacrifice the programming model in
favor of statelessness a little. I'm not really sure it's worth it.
-Matej
On 5/3/07, Jeremy Thomerson [EMAIL PROTECTED] wrote:
I know that I read somewhere
Stateless pages are available even in 1.2, but much more limited.
Basically, when you have no callbacks, you're page will be stateless
and not kept in memory. You'd have to do everything with bookmarkable
pages, links and page parameters then.
In 1.3, you can use some callbacks while still
Thanks to everyone for their help - I'm starting right away to convert
everything to detachable models for all domain objects that are loaded into
components...
Eelco, I am curious about your statement when you have no callbacks, you're
page will be stateless and not kept in memory... Most of
please we need something in wicket-examples on this wicket stateless best
pratice cuz it still kind of not easy pulling the whole stuff together at
times. it would be nice to have some 4-page example that shows best
practices for stateless arch.
thanks
On 5/3/07, Jeremy Thomerson [EMAIL
Thanks to everyone for their help - I'm starting right away to convert
everything to detachable models for all domain objects that are loaded into
components...
If you're only working with stateless pages, you don't detachable
models as those pages won't be stored to start with. But if you
There already is an example though. Take a look at
org.apache.wicket.examples.stateless.
If you have suggestions (patches) to extend that example even more,
that'd be great, but there's really not that much to say about it I
think.
Eelco
On 5/3/07, Ayodeji Aladejebi [EMAIL PROTECTED] wrote:
I know that I read somewhere that there is, or is going to be, a way to run
your wicket application without creating a session (until absolutely
necessary). We have a site that has mostly been converted to Wicket now,
and almost all of it is state-less data The URLs are all bookmarkable
detachable models are a must.
in my experience a wicket page is only about 50kb on average. that would
hardly cause an OOME on a server. 1.3 has second level session store that
pages to disk, so that is something else you might want to try.
once you convert to detachable models oomes should go
a large community site :-)
Maciej
- Original Message -
From: Igor Vaynberg
To: [EMAIL PROTECTED] ; wicket-user@lists.sourceforge.net
Sent: Thursday, May 03, 2007 7:27 AM
Subject: Re: [Wicket-user] Sessionless Wicket?
detachable models are a must.
in my experience a wicket
14 matches
Mail list logo
