Hi Per

Very nice article. It's good for newcommers and I even saw a thing or two
thats new for me.

About  the "avoid visible()!" part have you tried shiro or wicket security
to manage rendering of your components, I dont know if they just do a set
visible but if they don't it would sure make the code a lot nicer.. Now
thinking of it, one could make a simple annotation or maybe something else
that would replace all components that had setVisible(false) with a
webmarkup container..

Btw are you using IOC preferly guice and have any tips for optimizing this?

regards Nino

2011/3/1 Per <[email protected]>

> Hi Antoine,
>
> I have started collecting my hints over here:
>
> http://www.small-improvements.com/blog/technical/tuning-wicket-session-size
>
> Please note that much of it may be considered hacks and bad practice (I
> am just a Wicket user, not a Wicket master). There may be better ways to
> achieve the same results. I'd love to get feedback on these suggestions!
> So give it a shot and tell me how you went!
>
> Good luck!
> Per
>
>
> > *bump*
> >
> > I'm one of those people who is reading :-)
> >
> >
> > Antoine
> >
> >
> > On Mon, Feb 21, 2011 at 3:11 PM, Per <[hidden email]
> > </user/SendEmail.jtp?type=node&node=3330006&i=0>> wrote:
> >
> > >
> > >
> > > Hi,
> > >
> > > I am measuring it in a profiler after the request has been completed,
> > > but thanks for the hint.
> > >
> > > In case anyone else is reading, I have been playing with the
> > > onComponentTag() and onComponentTagBody() methods on the weekend, and
> > > I've been able to reduce my page sizes significantly. Admittedly, this
> > > comes at the expense of flexibility and beauty, but I'm only doing this
> > > in the inner loops of very few pages, so who cares :-)  Will write a
> > > summary with a couple of hints once I stop drowning in work.
> > >
> > > Cheers,
> > > Per
> > >
> > >
> > >> > Reading in the other thread that a session size of 100K or less
> > >> > is achievable, I'll admit defeat now: I have not been able to shrink
> > >> some of
> > >> > my pages(!) to less than 200K, not to mention the sessions. Despite
> > >> LDMs,
> > >> > CompoundPropertyModels, and no, there are no domain objects in
> > >> there, and no
> > >> > finals.
> > >>
> > >> How are you measuring this? Keep in mind that if you calculate when a
> > >> request is still processing, you might still be measuring temporary
> > >> data (e.g. for LoadableDetachableModel, you would also measure the
> > >> transientModelObject, and same for any proxies (Spring/ Guice) you
> > >> might use.
> > >>
> > >> Eelco
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [hidden email]
> > >> </user/SendEmail.jtp?type=node&node=3316743&i=0>
> > >> For additional commands, e-mail: [hidden email]
> > >> </user/SendEmail.jtp?type=node&node=3316743&i=1>
> > >>
> > >>
> > >>
> > >>
> > ------------------------------------------------------------------------
> > >> If you reply to this email, your message will be added to the
> > >> discussion below:
> > >>
> >
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3316743.html
> > <
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3316743.html?by-user=t
> >
> > >>
> > >> To unsubscribe from Just 100K per session? That would be my dream come
> > >> true! (Anyone here who has tuned session size before?), click here
> > >>
> > <
> http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3308014&code=cGVyQGhhbWJ1cmcuZGV8MzMwODAxNHwtMjI2MTAwMzE0
> > <
> http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3308014&code=cGVyQGhhbWJ1cmcuZGV8MzMwODAxNHwtMjI2MTAwMzE0&by-user=t
> >>.
> >
> > >>
> > >
> > >
> > > --
> > > View this message in context:
> >
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3317403.html
> > <
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3317403.html?by-user=t
> >
> > > Sent from the Users forum mailing list archive at Nabble.com.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > </user/SendEmail.jtp?type=node&node=3330006&i=1>
> > > For additional commands, e-mail: [hidden email]
> > </user/SendEmail.jtp?type=node&node=3330006&i=2>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > </user/SendEmail.jtp?type=node&node=3330006&i=3>
> > For additional commands, e-mail: [hidden email]
> > </user/SendEmail.jtp?type=node&node=3330006&i=4>
> >
> >
> >
> > ------------------------------------------------------------------------
> > If you reply to this email, your message will be added to the
> > discussion below:
> >
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3330006.html
> >
> > To unsubscribe from Just 100K per session? That would be my dream come
> > true! (Anyone here who has tuned session size before?), click here
> > <
> http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3308014&code=cGVyQGhhbWJ1cmcuZGV8MzMwODAxNHwtMjI2MTAwMzE0
> >.
> >
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Just-100K-per-session-That-would-be-my-dream-come-true-Anyone-here-who-has-tuned-session-size-before-tp3308014p3330425.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to