Hi, Yes, you can create your own org.apache.wicket.session.ISessionStore. See the default org.apache.wicket.session.HttpSessionStore for inspiration. To setup it: org.apache.wicket.Application#setSessionStoreProvider()
On Wed, Jan 9, 2013 at 8:05 PM, Jens Jahnke <[email protected]> wrote: > On Wed, 9 Jan 2013 18:14:51 +0100 > Martijn Dashorst <[email protected]> wrote: > > MD> > Would the app benefit from rolling out more dynos? > MD> > MD> If your app is stateful and depends on the session: > MD> it would suck, because heroku doesn't support sticky sessions. > MD> Therefore requests will be sent to different dynos and several of > MD> Wicket's features will not work. > MD> > MD> if it isn't stateful and doesn't depend on container session state, > MD> then you might be able to benefit from more dynos. > > Thanks for the information. It is a stateful app. :-( > > Could it be a workaround to store the session in a redis-store and is > this possible with wicket? > > Regards, > > Jens > > -- > 09. Hartung 2013, 19:01 > Homepage : http://www.jan0sch.de > > Victory uber allies! > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
