It will be the same. If you don't provide your own authentication strategy then no-op one is used that always returns "allowed". I.e. the calls to the authen strategy are executed always. You just need to replace it with your cookie checking one. But see org.apache.wicket.authentication.strategy.DefaultAuthenticationStrategy, it also works with cookie.
On Sun, Apr 1, 2012 at 9:29 AM, kshitiz <[email protected]> wrote: > Ok...thank you for replying...I wanted to ask one more thing? I am thinking > to add wicket authentication in my app. But as there would be only one type > of user only....should I use wicket authentication? I mean this can be > achieved by simple checking session existence also. Will there be any effect > in application performance in terms of speed if I use wicket authentication? > Please suggest me what will be best for me... > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-cookie-timeout-example-tp4521200p4522929.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] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
