is not required.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DataView-and-increasing-session-size-tp1876757p4652739.html
Sent from the Users forum mailing list archive at Nabble.com
Probably I was a bit unclear, I was talking about the serialized session
on disk. Does the should not grow aspect apply there, too?
J.
Igor Vaynberg wrote:
considering wicket only keeps last-accessed page in session your
session shouldnt just keep growing...
-igor
On Thu, Jan 29, 2009 at
yes it grows until a max
public DiskPageStore()
{
this((int)Bytes.megabytes(10).bytes(),
(int)Bytes.megabytes(100).bytes(), 50);
}
(10MB for one pagemap and 100MB for a complete session over multiply
pagemaps)
On Fri, Jan 30, 2009 at 09:44, Jürgen Lind juergen.l...@iteratec.de
Thank you for pointing me to the means to tune the DiskPagestore size.
The only question that remains is whether it is normal that it keeps growing
and by what extend.
J.
Johan Compagner wrote:
yes it grows until a max
public DiskPageStore()
{
yes until the default 10MB i already said that.
On Fri, Jan 30, 2009 at 09:58, Jürgen Lind juergen.l...@iteratec.de wrote:
Thank you for pointing me to the means to tune the DiskPagestore size.
The only question that remains is whether it is normal that it keeps
growing
and by what
Thank you for clarifying. The reason for for me asking these questions
is that it will be asked the very same questions once I recommend using
Wicket for the re-implementation of an existing application. I just want
to make sure that I have the correct answers :-)
J.
Johan Compagner wrote:
yes
Hi,
I have a question on how the DataView component is supposed to work. In my
application, I have to show quite large list of entities and so I am using
a DataView together with LoadableDetachableModels to read the data on demand.
However, when looking at the serialized sessions, I can observe
in context:
http://www.nabble.com/DataView-and-increasing-session-size-tp21723557p21724558.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
After some twiddling I found that the PagingNavigator seems to be the culprit.
If I leave it out, the session grows only moderately, when I put it in, the
domain objects end up in the session... Anyway here is the code:
public class AuftragUebersicht extends MasterLayout {
@SpringBean
, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
Michael Sparer
http://talk-on-tech.blogspot.com
--
View this message in context:
http://www.nabble.com/DataView-and-increasing-session-size-tp21723557p21725913.html
Sent from
Michael,
thanks for your help, it significantly reduced the amount of session data.
Still, the session keeps growing... Is there any way to determine which
objects get serialized and where they are dangling? Removing the Serializable
interface helps me to spot my own classes but it does not work
One more thing: just as a rule of thumb, what would be a reasonable
amount of data that gets added to the session for a single request?
20k? 100k?
Regards,
J.
Michael Sparer wrote:
I took a cursory glance over your code and saw
item.add(new Link(update, new Model(auftrag))
this way the
considering wicket only keeps last-accessed page in session your
session shouldnt just keep growing...
-igor
On Thu, Jan 29, 2009 at 11:20 PM, Jürgen Lind juergen.l...@iteratec.de wrote:
One more thing: just as a rule of thumb, what would be a reasonable
amount of data that gets added to the
13 matches
Mail list logo
